All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/4] dpaa2-eth: Add support for Rx flow classification
Date: Tue, 02 Oct 2018 22:24:25 -0700 (PDT)	[thread overview]
Message-ID: <20181002.222425.1399672535568714853.davem@davemloft.net> (raw)
In-Reply-To: <1538390698-22073-1-git-send-email-ruxandra.radulescu@nxp.com>

From: Ioana Radulescu <ruxandra.radulescu@nxp.com>
Date: Mon,  1 Oct 2018 13:44:54 +0300

> The Management Complex (MC) firmware initially allowed the
> configuration of a single key to be used both for Rx flow hashing
> and flow classification. This prevented us from supporting
> Rx flow classification independently of the hash key configuration.
> 
> Newer firmware versions expose separate commands for
> configuring the two types of keys, so we can use them to
> introduce Rx classification support. For frames that don't match
> any classification rule, we fall back to statistical distribution
> based on the current hash key.
> 
> The first patch in this set updates the Rx hashing code to use
> the new firmware API for key config. Subsequent patches introduce
> the firmware API for configuring the classification and actual
> support for adding and deleting rules via ethtool.

Series applied, thanks.

      parent reply	other threads:[~2018-10-03 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 10:44 [PATCH net-next 0/4] dpaa2-eth: Add support for Rx flow classification Ioana Radulescu
2018-10-01 10:44 ` [PATCH net-next 1/4] dpaa2-eth: Use new API for Rx flow hashing Ioana Radulescu
2018-10-01 10:44 ` [PATCH net-next 2/4] dpaa2-eth: Rename structure Ioana Radulescu
2018-10-01 10:44 ` [PATCH net-next 3/4] dpaa2-eth: Configure Rx flow classification key Ioana Radulescu
2018-10-01 10:44 ` [PATCH net-next 4/4] dpaa2-eth: Add ethtool support for flow classification Ioana Radulescu
2018-10-03  5:24 ` 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=20181002.222425.1399672535568714853.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 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.