All of
 help / color / mirror / Atom feed
From: Andrew Lunn <>
To: Alexander Lobakin <>
Cc: "David S. Miller" <>,
	Muciri Gatimu <>,
	Shashidhar Lakkavalli <>,
	John Crispin <>,
	Vivien Didelot <>,
	Florian Fainelli <>,
	Stanislav Fomichev <>,
	Daniel Borkmann <>,
	Song Liu <>,
	Alexei Starovoitov <>,
	Matteo Croce <>,
	Jakub Sitnicki <>,
	Eric Dumazet <>,
	Paul Blakey <>,
	Yoshiki Komachi <>,,
Subject: Re: [PATCH net] net: dsa: fix flow dissection on Tx path
Date: Thu, 5 Dec 2019 15:01:32 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Hi,
> > What i'm missing here is an explanation why the flow dissector is
> > called here if the protocol is already set? It suggests there is a
> > case when the protocol is not correctly set, and we do need to look
> > into the frame?
> If we have a device with multiple Tx queues, but XPS is not configured
> or system is running on uniprocessor system, then networking core code
> selects Tx queue depending on the flow to utilize as much Tx queues as
> possible but without breaking frames order.
> This selection happens in net/core/dev.c:skb_tx_hash() as:
> reciprocal_scale(skb_get_hash(skb), qcount)
> where 'qcount' is the total number of Tx queues on the network device.
> If skb has not been hashed prior to this line, then skb_get_hash() will
> call flow dissector to generate a new hash. That's why flow dissection
> can occur on Tx path.

Hi Alexander

So it looks like you are now skipping this hash. Which in your
testing, give better results, because the protocol is already set
correctly. But are there cases when the protocol is not set correctly?
We really do need to look into the frame?

How about when an outer header has just been removed? The frame was
received on a GRE tunnel, the GRE header has just been removed, and
now the frame is on its way out? Is the protocol still GRE, and we
should look into the frame to determine if it is IPv4, ARP etc?

Your patch looks to improve things for the cases you have tested, but
i'm wondering if there are other use cases where we really do need to
look into the frame? In which case, your fix is doing the wrong thing.
Should we be extending the tagger to handle the TX case as well as the
RX case?


  reply	other threads:[~2019-12-05 14:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 10:02 [PATCH net] net: dsa: fix flow dissection on Tx path Alexander Lobakin
2019-12-05 12:58 ` Andrew Lunn
2019-12-05 13:34   ` Alexander Lobakin
2019-12-05 14:01     ` Andrew Lunn [this message]
2019-12-05 14:58       ` Alexander Lobakin
2019-12-06  3:32         ` Florian Fainelli
2019-12-06  7:37           ` Alexander Lobakin
2019-12-06 18:05             ` Florian Fainelli
2019-12-06  3:28 ` Florian Fainelli
2019-12-06 15:06   ` Alexander Lobakin
2019-12-06 19:32 ` Rainer Sickinger
2019-12-07  4:19 ` David Miller
2019-12-07  8:10   ` Alexander Lobakin

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.