From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] shaper team forming up
Date: Mon, 14 Mar 2011 21:24:37 +0100 [thread overview]
Message-ID: <1300134277.2649.19.camel@edumazet-laptop> (raw)
In-Reply-To: <5BC42741-852B-4699-BA5D-D70B8D610D96@gmail.com>
Le lundi 14 mars 2011 à 21:55 +0200, Jonathan Morton a écrit :
> On 14 Mar, 2011, at 9:26 pm, Dave Täht wrote:
>
> > Over the weekend, Dan Siemons uncovered a possible bad interaction
> > between ECN and the default pfifo_fast qdisc in Linux.
> >
> > http://www.coverfire.com/archives/2011/03/13/pfifo_fast-and-ecn/
>
> This seems to be more complicated that it appears. It looks as though
> Linux has re-used the LSB of the old TOS field for some "link local"
> flag which is used by routing.
>
> It's not immediately obvious whether pfifo_fast is using this new
> interpretation though. If it isn't, the fix should be to remove the
> RTO_ONLINK bit from the mask it's using on the tos field. The other
> half of the mask correctly excludes the ECN bits from the field.
>
CC netdev, where linux network dev can take a look.
I would say that this is a wrong analysis :
1) ECN uses two low order bits of TOS byte
2) pfifo_fast uses skb->priority
skb->priority = rt_tos2priority(iph->tos);
#define IPTOS_TOS_MASK 0x1E
#define IPTOS_TOS(tos) ((tos)&IPTOS_TOS_MASK)
static inline char rt_tos2priority(u8 tos)
{
return ip_tos2prio[IPTOS_TOS(tos)>>1];
}
No interference between two mechanisms, unless sysadmin messed up things
(skb_edit)
prev parent reply other threads:[~2011-03-14 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:26 Dave Täht
2011-03-14 19:55 ` Jonathan Morton
2011-03-14 20:24 ` Eric Dumazet [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.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300134277.2649.19.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=netdev@vger.kernel.org \
/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