From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Sebastian Moeller <moeller0@gmx.de>, Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some kernel updates + new userspace patch
Date: Fri, 30 Aug 2013 17:46:31 +0200 [thread overview]
Message-ID: <20130830174631.743e25ce@redhat.com> (raw)
In-Reply-To: <5BEF0C7C-C2F4-45A9-9FF2-E32A05B8D67B@gmx.de>
[long-thread-cut]
Sebastian, noted at some point that is was difficult to determine if
the tc configuration were using the linklayer option.
I have posted a patch against iproute2/tc, that implement reading out
the linklayer setting (requires my kernel patch discussed in this
thread).
See:
http://thread.gmane.org/gmane.linux.network/281876
This patch also sends the linklayer option to the kernel directly,
which mean that the kernel don't need to perform linklayer detection
based on the rate table (which were not accurate at rates above
100Mbit/s).
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2013-08-30 15:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 18:42 [Cerowrt-devel] some kernel updates Dave Taht
[not found] ` <56B261F1-2277-457C-9A38-FAB89818288F@gmx.de>
[not found] ` <CAA93jw6ku0OOXzNcAUtK4UL5uc7R2zVAOKo1+Fwzmr7gCH1pzA@mail.gmail.com>
[not found] ` <2148E2EF-A119-4499-BAC1-7E647C53F077@gmx.de>
2013-08-23 0:52 ` Sebastian Moeller
2013-08-23 5:13 ` Dave Taht
2013-08-23 7:27 ` Jesper Dangaard Brouer
2013-08-23 10:15 ` Sebastian Moeller
2013-08-23 11:16 ` Jesper Dangaard Brouer
2013-08-23 12:37 ` Sebastian Moeller
2013-08-23 13:02 ` Fred Stratton
2013-08-23 19:49 ` Sebastian Moeller
2013-08-23 15:05 ` Jesper Dangaard Brouer
2013-08-23 17:23 ` Toke Høiland-Jørgensen
2013-08-23 20:09 ` Sebastian Moeller
2013-08-23 20:46 ` Toke Høiland-Jørgensen
2013-08-24 20:51 ` Sebastian Moeller
2013-08-23 19:51 ` Sebastian Moeller
2013-08-23 9:16 ` Sebastian Moeller
2013-08-23 19:38 ` Sebastian Moeller
2013-08-23 19:47 ` Dave Taht
2013-08-23 19:56 ` Sebastian Moeller
2013-08-23 20:29 ` Dave Taht
2013-08-24 20:51 ` Sebastian Moeller
2013-08-24 20:51 ` Sebastian Moeller
2013-08-25 9:21 ` Fred Stratton
2013-08-25 10:17 ` Fred Stratton
2013-08-25 13:59 ` Sebastian Moeller
2013-08-25 14:26 ` Fred Stratton
2013-08-25 14:31 ` Fred Stratton
2013-08-25 17:53 ` Sebastian Moeller
2013-08-25 17:55 ` Dave Taht
2013-08-25 18:00 ` Fred Stratton
2013-08-25 18:30 ` Fred Stratton
2013-08-25 18:41 ` Dave Taht
2013-08-25 19:08 ` Fred Stratton
2013-08-25 19:31 ` Fred Stratton
2013-08-25 21:54 ` Sebastian Moeller
2013-08-25 20:28 ` Dave Taht
2013-08-25 21:40 ` Sebastian Moeller
2013-08-25 21:50 ` Sebastian Moeller
2013-08-27 11:10 ` Jesper Dangaard Brouer
2013-08-27 10:45 ` Jesper Dangaard Brouer
2013-08-30 15:46 ` Jesper Dangaard Brouer [this message]
2013-08-27 10:42 ` Jesper Dangaard Brouer
2013-08-24 23:08 ` Sebastian Moeller
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.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130830174631.743e25ce@redhat.com \
--to=jbrouer@redhat.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox