Toke Høiland-Jørgensen writes: > flent-users writes: > >> On Tue, Jan 8, 2019 at 3:34 AM Toke Høiland-Jørgensen < >> notifications@github.com> wrote: >> >>> So, finally got around to look at this. Wow, that's an annoying > change for >>> the Flent use case. Did you find a workaround? >>> >> >> Other than ripping out the relevant commit or writing the netlnk > code from >> scratch? No. It's a pretty crippling change. Lemmee forward where > the convo >> stalled out. > > Right. I guess I'll go write a monitor mode for iproute2 and see if > it'll be accepted upstream... > > But yeah, Steven's suggestion about just adding a flag was also my > first > thought... It would be nice for this facility to work again. I have not been doing any kernel-related work for a while, but will gladly test, as usual, if you come up with something. I happen to prefer the idea of the generic monitoring mode with high resolution timing support. Alternatively updating the common "watch" utilities to have better than 1sec resolution would be good. > > -Toke > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/146#issuecomment-455785969