Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Davide Caratti <dcaratti@redhat.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, cake@lists.bufferbloat.net,
	Jiri Pirko <jiri@resnulli.us>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Ilya Ponetayev <i.ponetaev@ndmsystems.com>,
	Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: [Cake] [PATCH net] sched: consistently handle layer3 header accesses in the presence of VLANs
Date: Fri, 03 Jul 2020 14:53:50 +0200	[thread overview]
Message-ID: <4297936b4cc7d6cdcb51ccc10331467f39978795.camel@redhat.com> (raw)
In-Reply-To: <20200703120523.465334-1-toke@redhat.com>

hello Toke,

thanks for answering!

On Fri, 2020-07-03 at 14:05 +0200, Toke Høiland-Jørgensen wrote:
>   while (proto == htons(ETH_P_8021Q) || proto == htons(ETH_P_8021AD)) {

maybe this line be shortened, since if_vlan.h has [1]:

while (eth_type_vlan(proto)) {
 	...
}

If I read well, the biggest change from functional point of view is that
now qdiscs can set the ECN bit also on non-accelerated VLAN packets and
QinQ-tagged packets, if the IP header is the outer-most header after VLAN;
and the same applies to almost all net/sched former users of skb->protocol 
or tc_skb_protocol().

Question (sorry in advance because it might be a dumb one :) ):

do you know why cls_flower, act_ct, act_mpls and act_connmark keep reading
skb->protocol? is that intentional?

(for act_mpls that doesn't look intentional, and probably the result is
that the BOS bit is not set correctly if someone tries to push/pop a label
for a non-accelerated or QinQ packet. But I didn't try it experimentally
:) )

[1] https://elixir.bootlin.com/linux/latest/source/include/linux/if_vlan.h#L300

-- 
davide



  reply	other threads:[~2020-07-03 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 12:05 Toke Høiland-Jørgensen
2020-07-03 12:53 ` Davide Caratti [this message]
2020-07-03 14:37   ` Toke Høiland-Jørgensen

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4297936b4cc7d6cdcb51ccc10331467f39978795.camel@redhat.com \
    --to=dcaratti@redhat.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=davem@davemloft.net \
    --cc=i.ponetaev@ndmsystems.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=toke@redhat.com \
    --cc=xiyou.wangcong@gmail.com \
    /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