From: "Dave Täht" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Comment <comment@noreply.github.com>,
flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] [tohojo/flent] tc_iterate.c is borken for newer tcs (#146)
Date: Sat, 19 Jan 2019 06:40:19 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/146/455785969@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/146@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 1498 bytes --]
Toke Høiland-Jørgensen <notifications@github.com> writes:\r
\r
> flent-users <notifications@github.com> writes:\r
>\r
>> On Tue, Jan 8, 2019 at 3:34 AM Toke Høiland-Jørgensen <\r
>> notifications@github.com> wrote:\r
>>\r
>>> So, finally got around to look at this. Wow, that's an annoying\r
> change for\r
>>> the Flent use case. Did you find a workaround?\r
>>>\r
>>\r
>> Other than ripping out the relevant commit or writing the netlnk\r
> code from\r
>> scratch? No. It's a pretty crippling change. Lemmee forward where\r
> the convo\r
>> stalled out.\r
>\r
> Right. I guess I'll go write a monitor mode for iproute2 and see if\r
> it'll be accepted upstream...\r
>\r
> But yeah, Steven's suggestion about just adding a flag was also my\r
> first\r
> thought...\r
\r
It would be nice for this facility to work again. I have not been doing\r
any kernel-related work for a while, but will gladly test, as usual, if\r
you come up with something. I happen to prefer the idea of the generic\r
monitoring mode with high resolution timing support. Alternatively\r
updating the common "watch" utilities to have better than 1sec\r
resolution would be good.\r
\r
>\r
> -Toke\r
>\r
> —\r
> You are receiving this because you authored the thread.\r
> Reply to this email directly, view it on GitHub, or mute the thread.\r
\r
\r
-- \r
You are receiving this because you commented.\r
Reply to this email directly or view it on GitHub:\r
https://github.com/tohojo/flent/issues/146#issuecomment-455785969
[-- Attachment #1.2: Type: text/html, Size: 4908 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
prev parent reply other threads:[~2019-01-19 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tohojo/flent/issues/146@github.com>
2018-08-18 23:19 ` Dave Täht
2019-01-08 11:34 ` Toke Høiland-Jørgensen
2019-01-08 15:06 ` Toke Høiland-Jørgensen
2019-01-19 14:40 ` Dave Täht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issues/146/455785969@github.com \
--to=notifications@github.com \
--cc=comment@noreply.github.com \
--cc=flent-users@flent.org \
--cc=flent@noreply.github.com \
--cc=reply+01ead4bf5e16a3c8a895fb0bb06f4e92ea1704a6d8a5352e92cf00000001185af8d392a169ce14a4085a@reply.github.com \
--subject='Re: [Flent-users] [tohojo/flent] tc_iterate.c is borken for newer tcs (#146)' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox