netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Edward Cree <ecree@solarflare.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v4 net-next 0/9] Handle multiple received packets at each stage
Date: Mon, 2 Jul 2018 09:40:57 -0600	[thread overview]
Message-ID: <d7092205-ff36-e982-e8fb-1a056df8b0bc@gmail.com> (raw)
In-Reply-To: <5bf84d99-8f77-54ee-7543-ada13a730361@solarflare.com>

On 7/2/18 9:11 AM, Edward Cree wrote:
> This patch series adds the capability for the network stack to receive a
>  list of packets and process them as a unit, rather than handling each
>  packet singly in sequence.  This is done by factoring out the existing
>  datapath code at each layer and wrapping it in list handling code.
> 

...

>  drivers/net/ethernet/sfc/efx.c        |  12 +++
>  drivers/net/ethernet/sfc/net_driver.h |   3 +
>  drivers/net/ethernet/sfc/rx.c         |   7 +-
>  include/linux/list.h                  |  30 ++++++
>  include/linux/netdevice.h             |   4 +
>  include/linux/netfilter.h             |  22 +++++
>  include/net/ip.h                      |   2 +
>  include/trace/events/net.h            |   7 ++
>  net/core/dev.c                        | 174 ++++++++++++++++++++++++++++++++--
>  net/ipv4/af_inet.c                    |   1 +
>  net/ipv4/ip_input.c                   | 114 ++++++++++++++++++++--
>  11 files changed, 360 insertions(+), 16 deletions(-)
> 

Nice work. Have you looked at IPv6 support yet?

  parent reply	other threads:[~2018-07-02 15:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 15:11 [PATCH v4 net-next 0/9] Handle multiple received packets at each stage Edward Cree
2018-07-02 15:12 ` [PATCH v4 net-next 1/9] net: core: trivial netif_receive_skb_list() entry point Edward Cree
2018-07-02 15:12 ` [PATCH v4 net-next 2/9] sfc: batch up RX delivery Edward Cree
2018-07-02 15:13 ` [PATCH v4 net-next 3/9] net: core: unwrap skb list receive slightly further Edward Cree
2018-07-02 15:13 ` [PATCH v4 net-next 4/9] net: core: Another step of skb receive list processing Edward Cree
2018-07-02 15:13 ` [PATCH v4 net-next 5/9] net: core: another layer of lists, around PF_MEMALLOC skb handling Edward Cree
2018-07-02 15:13 ` [PATCH v4 net-next 6/9] net: core: propagate SKB lists through packet_type lookup Edward Cree
2018-07-02 15:14 ` [PATCH v4 net-next 7/9] net: ipv4: listified version of ip_rcv Edward Cree
2018-07-03 10:50   ` Pablo Neira Ayuso
2018-07-03 12:13     ` Florian Westphal
2018-07-04 16:01   ` Edward Cree
2018-07-02 15:14 ` [PATCH v4 net-next 8/9] net: ipv4: listify ip_rcv_finish Edward Cree
2018-07-02 15:14 ` [PATCH v4 net-next 9/9] net: don't bother calling list RX functions on empty lists Edward Cree
2018-07-02 15:40 ` David Ahern [this message]
2018-07-02 18:09   ` [PATCH v4 net-next 0/9] Handle multiple received packets at each stage Edward Cree
2018-07-03  7:51   ` Paolo Abeni
2018-07-04  5:09 ` 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=d7092205-ff36-e982-e8fb-1a056df8b0bc@gmail.com \
    --to=dsahern@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.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).