From: Stephen Hemminger <shemminger@vyatta.com>
To: Dimitris Michailidis <dm@chelsio.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] cxgb4: set skb->rxhash
Date: Tue, 27 Apr 2010 15:36:56 -0700 [thread overview]
Message-ID: <20100427153656.7bcaba83@nehalam> (raw)
In-Reply-To: <1272406825-11615-1-git-send-email-dm@chelsio.com>
On Tue, 27 Apr 2010 15:20:25 -0700
Dimitris Michailidis <dm@chelsio.com> wrote:
> Implement the ->set_flags ethtool method to control NETIF_F_RXHASH and
> set skb->rxhash to the HW calculated hash accordingly.
>
> Signed-off-by: Dimitris Michailidis <dm@chelsio.com>
> ---
> drivers/net/cxgb4/cxgb4_main.c | 15 ++++++++++++++-
> drivers/net/cxgb4/sge.c | 7 ++++++-
> drivers/net/cxgb4/t4_msg.h | 1 +
> 3 files changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/cxgb4/cxgb4_main.c b/drivers/net/cxgb4/cxgb4_main.c
> index 5f582db..1bad500 100644
> --- a/drivers/net/cxgb4/cxgb4_main.c
> +++ b/drivers/net/cxgb4/cxgb4_main.c
> @@ -1711,6 +1711,18 @@ static int set_tso(struct net_device *dev, u32 value)
> return 0;
> }
>
> +static int set_flags(struct net_device *dev, u32 flags)
> +{
> + if (flags & ~ETH_FLAG_RXHASH)
> + return -EOPNOTSUPP;
> +
> + if (flags & ETH_FLAG_RXHASH)
> + dev->features |= NETIF_F_RXHASH;
> + else
> + dev->features &= ~NETIF_F_RXHASH;
> + return 0;
> +}
You need to check for and reject other values NTUPLE and LRO
next prev parent reply other threads:[~2010-04-27 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 22:20 [PATCH net-next] cxgb4: set skb->rxhash Dimitris Michailidis
2010-04-27 22:36 ` Stephen Hemminger [this message]
2010-04-27 22:39 ` Dimitris Michailidis
2010-04-27 22:44 ` David Miller
2010-04-27 22:43 ` Eric Dumazet
2010-04-27 22:45 ` David Miller
2010-04-27 22:43 ` David Miller
2010-04-27 22:46 ` Dimitris Michailidis
2010-04-27 22:47 ` David Miller
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=20100427153656.7bcaba83@nehalam \
--to=shemminger@vyatta.com \
--cc=dm@chelsio.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;
as well as URLs for NNTP newsgroup(s).