From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.toke.dk X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-101.9 required=5.0 tests=BAYES_00,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.2 Received: from mail.toke.dk by mail.toke.dk with LMTP id qM/5CwQ3Q1zvTAAAOr1fkg (envelope-from ) for ; Sat, 19 Jan 2019 15:41:08 +0100 Received: from web6.sd.eurovps.com (web6.sd.eurovps.com [77.235.54.103]) by mail.toke.dk (Postfix) with ESMTPS id 1282B5B8717 for ; Sat, 19 Jan 2019 15:41:07 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=fail reason="key not found in DNS" (0-bit key) header.d=flent.org header.i=@flent.org header.b=KwwA+wLW; dkim=fail reason="signature verification failed" (1024-bit key) header.d=github.com header.i=@github.com header.b=Bd/HPCNv DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=flent.org; s=default; h=Sender:Content-Type:Cc:Reply-To:List-Subscribe:List-Help: List-Post:List-Archive:List-Unsubscribe:List-Id:Subject:Mime-Version: References:In-Reply-To:Message-ID:To:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=rxqSP+SdFJLRsR2F2Wh7D/7CTFYQk0MI1Jr0LOGd5TU=; b=KwwA+wLWEgl6kV1YSPAagxlH7c w56Ql23meN0qL3BV17dtEA390vfbry/0c98Ux358IV3oLCr0za8wc/x8oyXffYMB104lZ7LWao3RD 8v81SYjOrFvzUaGHhY54L9slBo08L4lDzoNixbMFxgFD9FoWi8kAK+SMAtyAMjwmEeSL4/15FIaCZ CLwrFkGnVjVcIIWuqyX2GHz8w7QmbEuwsDNOW9j0Ii5Q9rE4hhtQ4sqXJgDnAOaraTLHkueAkmicB zCNIjh+EODQJzjK3DxkHZiGEBUE13lDGQ2gEpMQ44lLXVN7BfnBi28ZmWKXw58qnqfvuN8KTUhiuz SxztUeMw==; Received: from [::1] (port=60158 helo=web6.sd.eurovps.com) by web6.sd.eurovps.com with esmtp (Exim 4.91) (envelope-from ) id 1gkro0-003o4m-F4; Sat, 19 Jan 2019 16:41:04 +0200 Received: from out-7.smtp.github.com ([192.30.252.198]:39729) by web6.sd.eurovps.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gkrnt-003nz4-JJ for flent-users@flent.org; Sat, 19 Jan 2019 16:41:00 +0200 Date: Sat, 19 Jan 2019 06:40:19 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547908819; bh=vPRN/xFjzA0Ihkb3EesdyaxpUss0Rc+xAb04crSUEyQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Bd/HPCNvEiaAAT5/T7ROKkw1tY0eewqpLg/WIUpGkPI7hqYg0hi3KS6v6+fcO5fqq T0sLWjpVLrMXofPu6otNJsD4qJcjt8la5fEFLCJRbj6jXsVMoyxds6TBweuRxMvo6K Z4ja4fQruvprnucXX5g8Bud/vkmpDvExK8DyC2fA= From: =?UTF-8?B?RGF2ZSBUw6RodA==?= To: tohojo/flent Message-ID: In-Reply-To: References: Mime-Version: 1.0 Precedence: list X-GitHub-Sender: dtaht X-GitHub-Recipient: flent-users X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: flent-users@flent.org Subject: Re: [Flent-users] [tohojo/flent] tc_iterate.c is borken for newer tcs (#146) X-BeenThere: flent-users@flent.org X-Mailman-Version: 2.1.27 List-Id: Flent discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: tohojo/flent Cc: Comment , flent-users Content-Type: multipart/mixed; boundary="===============6845623069607124863==" Errors-To: flent-users-bounces@flent.org Sender: "Flent-users" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - web6.sd.eurovps.com X-AntiAbuse: Original Domain - toke.dk X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - flent.org X-Get-Message-Sender-Via: web6.sd.eurovps.com: acl_c_authenticated_local_user: mailman/mailman X-Authenticated-Sender: web6.sd.eurovps.com: mailman@flent.org --===============6845623069607124863== Content-Type: multipart/alternative; boundary="--==_mimepart_5c4336d318bed_122c3fe2dfad45c41147171"; charset=UTF-8 Content-Transfer-Encoding: 7bit ----==_mimepart_5c4336d318bed_122c3fe2dfad45c41147171 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Toke H=C3=B8iland-J=C3=B8rgensen writes:=0D =0D > flent-users writes:=0D >=0D >> On Tue, Jan 8, 2019 at 3:34 AM Toke H=C3=B8iland-J=C3=B8rgensen <=0D >> notifications@github.com> wrote:=0D >>=0D >>> So, finally got around to look at this. Wow, that's an annoying=0D > change for=0D >>> the Flent use case. Did you find a workaround?=0D >>>=0D >>=0D >> Other than ripping out the relevant commit or writing the netlnk=0D > code from=0D >> scratch? No. It's a pretty crippling change. Lemmee forward where=0D > the convo=0D >> stalled out.=0D >=0D > Right. I guess I'll go write a monitor mode for iproute2 and see if=0D > it'll be accepted upstream...=0D >=0D > But yeah, Steven's suggestion about just adding a flag was also my=0D > first=0D > thought...=0D =0D It would be nice for this facility to work again. I have not been doing=0D= any kernel-related work for a while, but will gladly test, as usual, if=0D= you come up with something. I happen to prefer the idea of the generic=0D= monitoring mode with high resolution timing support. Alternatively=0D updating the common "watch" utilities to have better than 1sec=0D resolution would be good.=0D =0D >=0D > -Toke=0D >=0D > =E2=80=94=0D > You are receiving this because you authored the thread.=0D > Reply to this email directly, view it on GitHub, or mute the thread.=0D= =0D =0D -- =0D You are receiving this because you commented.=0D Reply to this email directly or view it on GitHub:=0D https://github.com/tohojo/flent/issues/146#issuecomment-455785969= ----==_mimepart_5c4336d318bed_122c3fe2dfad45c41147171 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Toke H=C3=B8iland-J=C3=B8rgensen <notifications@github.com> writes:=
=0D
=0D > flent-users <notifications@github.com> writes:
=0D >
=0D >> On Tue, Jan 8, 2019 at 3:34 AM Toke H=C3=B8iland-J=C3=B8rgensen = <
=0D >> notifications@github.com> wrote:
=0D >>
=0D >>> So, finally got around to look at this. Wow, that's an a= nnoying
=0D > change for
=0D >>> the Flent use case. Did you find a workaround?
=0D >>>
=0D >>
=0D >> Other than ripping out the relevant commit or writing the netlnk=
=0D > code from
=0D >> scratch? No. It's a pretty crippling change. Lemmee forward = where
=0D > the convo
=0D >> stalled out.
=0D >
=0D > Right. I guess I'll go write a monitor mode for iproute2 and see= if
=0D > it'll be accepted upstream...
=0D >
=0D > But yeah, Steven's suggestion about just adding a flag was also = my
=0D > first
=0D > thought...
=0D
=0D It would be nice for this facility to work again. I have not been doing=0D any kernel-related work for a while, but will gladly test, as usual, if=0D you come up with something. I happen to prefer the idea of the generic=0D monitoring mode with high resolution timing support. Alternatively
=0D= updating the common "watch" utilities to have better than 1sec<= br>=0D resolution would be good.
=0D
=0D >
=0D > -Toke
=0D >
=0D > =E2=80=94
=0D > You are receiving this because you authored the thread.
=0D > Reply to this email directly, view it on GitHub, or mute the thread.=
=0D =0D =0D

&m= dash;
You are receiving this because you commented.
Reply to th= is email directly, view it on GitHub, or mute the thread.3D""

=0D =0D = ----==_mimepart_5c4336d318bed_122c3fe2dfad45c41147171-- --===============6845623069607124863== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org --===============6845623069607124863==--