netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: therbert@google.com (Tom Herbert)
To: davem@davemloft.net, netdev@vger.kernel.org
Subject: RFC [PATCH net-2.6 0/6] net: Software RSS implementation
Date: Wed,  5 Mar 2008 12:51:16 -0800 (PST)	[thread overview]
Message-ID: <20080305205116.5737141256E@localhost> (raw)

Hello,

This patch set contains code to support software Receive Side Scaling (RSS) for the networking receive path.  We have implemented two variants of RSS that addresses some issues we have seen with scaling networking:

1) The napi poll function for a device can be scheduled on a different CPU than the harware interrupt is received.  On architectures where the hardware interrupt is pinned on a single CPU, this allows us to round robin NAPI processing over a set of CPUs to balance the network processing load.

2) Packets received in the NAPI poll function for a NIC can be queued to other CPUs for stack processing (starting from netif_receive_skb).  We use a typical 4-tuple hash to direct packets on a connection to the same CPU.  This mechanism introduces some parallelism into the receive path which in turn increases our packets per second rate.

In this implementation we added the capability for a softirq to be scheduled on one CPU from another CPU; an IPI is used to kick processing on the target CPU.  Both variants of RSS allow a CPU mask which is set per device that indicates which CPUs are eligible for RSS.

These patches are done in the general networking code and do not require any changes to device drivers.  In particular, they are useful with devices that don't have support for hardware RSS.

I would appreciate any comments on this approach, escpecially if there are any ideas for improvement or related work.

Thanks,

Tom Herbert <therbert@google.com>


                 reply	other threads:[~2008-03-05 20:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080305205116.5737141256E@localhost \
    --to=therbert@google.com \
    --cc=davem@davemloft.net \
    --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).