From: Florian Fainelli <f.fainelli@gmail.com>
To: Petri Gynther <pgynther@google.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, jaedon.shin@gmail.com
Subject: Re: [PATCH net-next 0/7] net: bcmgenet: multiple Rx queues support
Date: Wed, 25 Mar 2015 15:32:38 -0700 [thread overview]
Message-ID: <55133786.40500@gmail.com> (raw)
In-Reply-To: <20150325193509.09C362201FB@puck.mtv.corp.google.com>
On 25/03/15 12:35, Petri Gynther wrote:
> Final patch set to add support for multiple Rx queues:
> 1. remove priv->int0_mask and priv->int1_mask
> 2. modify Tx ring int_enable and int_disable vectors
> 3. simplify bcmgenet_init_dma()
> 4. tweak init_umac()
> 5. rework Tx NAPI code
> 6. rework Rx NAPI code
> 7. add support for multiple Rx queues
>
Looks very good, thanks for getting these change out! Now I suppose what
we would need is some sort of ethtool rx-nfc API to allow flow
configuration towards particular RX queues?
--
Florian
next prev parent reply other threads:[~2015-03-25 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 19:35 [PATCH net-next 0/7] net: bcmgenet: multiple Rx queues support Petri Gynther
2015-03-25 22:32 ` Florian Fainelli [this message]
2015-03-25 22:53 ` Petri Gynther
2015-03-27 21:26 ` 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=55133786.40500@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=jaedon.shin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pgynther@google.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.