Toke Høiland-Jørgensen &lt;notifications@github.com&gt; writes:<br>

<br>

&gt; flent-users &lt;notifications@github.com&gt; writes:<br>

&gt;<br>

&gt;&gt; On Tue, Jan 8, 2019 at 3:34 AM Toke Høiland-Jørgensen &lt;<br>

&gt;&gt; notifications@github.com&gt; wrote:<br>

&gt;&gt;<br>

&gt;&gt;&gt; So, finally got around to look at this. Wow, that&#39;s an annoying<br>

&gt; change for<br>

&gt;&gt;&gt; the Flent use case. Did you find a workaround?<br>

&gt;&gt;&gt;<br>

&gt;&gt;<br>

&gt;&gt; Other than ripping out the relevant commit or writing the netlnk<br>

&gt; code from<br>

&gt;&gt; scratch? No. It&#39;s a pretty crippling change. Lemmee forward where<br>

&gt; the convo<br>

&gt;&gt; stalled out.<br>

&gt;<br>

&gt; Right. I guess I&#39;ll go write a monitor mode for iproute2 and see if<br>

&gt; it&#39;ll be accepted upstream...<br>

&gt;<br>

&gt; But yeah, Steven&#39;s suggestion about just adding a flag was also my<br>

&gt; first<br>

&gt; thought...<br>

<br>

It would be nice for this facility to work again. I have not been doing<br>

any kernel-related work for a while, but will gladly test, as usual, if<br>

you come up with something. I happen to prefer the idea of the generic<br>

monitoring mode with high resolution timing support. Alternatively<br>

updating the common &quot;watch&quot; utilities to have better than 1sec<br>

resolution would be good.<br>

<br>

&gt;<br>

&gt; -Toke<br>

&gt;<br>

&gt; —<br>

&gt; You are receiving this because you authored the thread.<br>

&gt; Reply to this email directly, view it on GitHub, or mute the thread.<br>





<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/tohojo/flent/issues/146#issuecomment-455785969">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AerUv2tPuoO873x0UlH_UOoNBSY3-7vqks5vEy5TgaJpZM4VouaY">mute the thread</a>.<img src="https://github.com/notifications/beacon/AerUv7NyDOq3dbOEi1lIm_-FUVQfO8F8ks5vEy5TgaJpZM4VouaY.gif" height="1" width="1" alt="" /></p>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/tohojo/flent","title":"tohojo/flent","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/tohojo/flent"}},"updates":{"snippets":[{"icon":"PERSON","message":"@dtaht in #146: Toke Høiland-Jørgensen \u003cnotifications@github.com\u003e writes:\n\n\u003e flent-users \u003cnotifications@github.com\u003e writes:\n\u003e\n\u003e\u003e On Tue, Jan 8, 2019 at 3:34 AM Toke Høiland-Jørgensen \u003c\n\u003e\u003e notifications@github.com\u003e wrote:\n\u003e\u003e\n\u003e\u003e\u003e So, finally got around to look at this. Wow, that's an annoying\n\u003e change for\n\u003e\u003e\u003e the Flent use case. Did you find a workaround?\n\u003e\u003e\u003e\n\u003e\u003e\n\u003e\u003e Other than ripping out the relevant commit or writing the netlnk\n\u003e code from\n\u003e\u003e scratch? No. It's a pretty crippling change. Lemmee forward where\n\u003e the convo\n\u003e\u003e stalled out.\n\u003e\n\u003e Right. I guess I'll go write a monitor mode for iproute2 and see if\n\u003e it'll be accepted upstream...\n\u003e\n\u003e But yeah, Steven's suggestion about just adding a flag was also my\n\u003e first\n\u003e thought...\n\nIt would be nice for this facility to work again. I have not been doing\nany kernel-related work for a while, but will gladly test, as usual, if\nyou come up with something. I happen to prefer the idea of the generic\nmonitoring mode with high resolution timing support. Alternatively\nupdating the common \"watch\" utilities to have better than 1sec\nresolution would be good.\n\n\u003e\n\u003e -Toke\n\u003e\n\u003e —\n\u003e You are receiving this because you authored the thread.\n\u003e Reply to this email directly, view it on GitHub, or mute the thread.\n"}],"action":{"name":"View Issue","url":"https://github.com/tohojo/flent/issues/146#issuecomment-455785969"}}}</script>

<script type="application/ld+json">[

{

"@context": "http://schema.org",

"@type": "EmailMessage",

"potentialAction": {

"@type": "ViewAction",

"target": "https://github.com/tohojo/flent/issues/146#issuecomment-455785969",

"url": "https://github.com/tohojo/flent/issues/146#issuecomment-455785969",

"name": "View Issue"

},

"description": "View this Issue on GitHub",

"publisher": {

"@type": "Organization",

"name": "GitHub",

"url": "https://github.com"

}

}

]</script>