All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Roland Dreier <roland@kernel.org>
Cc: Ben Hutchings <bhutchings@solarflare.com>, netdev@vger.kernel.org
Subject: Re: Best way to set kernel thread affinity for handling a socket?
Date: Thu, 23 Aug 2012 11:56:16 -0600	[thread overview]
Message-ID: <50366EC0.2060004@genband.com> (raw)
In-Reply-To: <CAG4TOxOdTiahqVo6+cD=mCN5Ov_hLa_m5gBTuj5sUYsM+GgnYw@mail.gmail.com>

On 08/23/2012 11:04 AM, Roland Dreier wrote:
> On Wed, Aug 22, 2012 at 9:21 AM, Ben Hutchings
> <bhutchings@solarflare.com>  wrote:
>> With RFS we try to do the reverse: move the packets to match the socket
>> user.   But it's not (yet) turned on by default.  See
>> Documentation/networking/scaling.txt
>
> Fair enough.  However I think at least in this case it sounds like extra
> overhead: it should be easy for us to do everything on the CPU where
> the packets are being received.

In the general case though RFS can be useful.  We have a server with one 
application instance per core.  It's beneficial to be able to steer 
packets destined for a given instance to an eth driver queue whose 
interrupt is handled by the cpu running that instance.

Depending on the hardware being used, it may be possible to do this more 
efficiently.  The ixgbe driver (if the feature is enabled) will 
periodically look at the outgoing tcp traffic and set up hardware flow 
filtering rules to direct incoming traffic for that connection to the 
queue that sent out the messages.

Chris

      parent reply	other threads:[~2012-08-23 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 16:10 Best way to set kernel thread affinity for handling a socket? Roland Dreier
2012-08-22 16:21 ` Ben Hutchings
2012-08-23 17:04   ` Roland Dreier
2012-08-23 17:51     ` Ben Hutchings
2012-08-23 17:56     ` Chris Friesen [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=50366EC0.2060004@genband.com \
    --to=chris.friesen@genband.com \
    --cc=bhutchings@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=roland@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 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.