From: David Miller <davem@davemloft.net>
To: ruxandra.radulescu@nxp.com
Cc: netdev@vger.kernel.org, ioana.ciornei@nxp.com
Subject: Re: [PATCH net-next] dpaa2-eth: Make Rx flow hash key configurable
Date: Mon, 24 Sep 2018 12:29:15 -0700 (PDT) [thread overview]
Message-ID: <20180924.122915.506780899873501609.davem@davemloft.net> (raw)
In-Reply-To: <20180924153611.25179-1-ruxandra.radulescu@nxp.com>
From: Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com>
Date: Mon, 24 Sep 2018 15:36:21 +0000
> Until now, the Rx flow hash key was a 5-tuple (IP src, IP dst,
> IP nextproto, L4 src port, L4 dst port) fixed value that we
> configured at probe.
>
> Add support for configuring this hash key at runtime.
> We support all standard header fields configurable through ethtool,
> but cannot differentiate between flow types, so the same hash key
> is applied regardless of protocol.
>
> We also don't support the discard option.
>
> Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
Applied.
prev parent reply other threads:[~2018-09-25 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 15:36 [PATCH net-next] dpaa2-eth: Make Rx flow hash key configurable Ioana Ciocoi Radulescu
2018-09-24 19:29 ` David Miller [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180924.122915.506780899873501609.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ioana.ciornei@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=ruxandra.radulescu@nxp.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