netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Yuehai Xu <yuehaixu@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>, <yhxu@wayne.edu>,
	<sbw@mit.edu>
Subject: Re: How do I know my driver support RSS?
Date: Sun, 4 Mar 2012 00:10:55 +0000	[thread overview]
Message-ID: <1330819855.8460.291.camel@deadeye> (raw)
In-Reply-To: <CAEc1PS1j2DL4m7B1Rp9nseqLWsxaXXY+ZJDHra+99c5-WPgYcQ@mail.gmail.com>

On Sat, 2012-03-03 at 16:25 -0500, Yuehai Xu wrote:
[...]
> Since I read the following statements from a paper, "we use a separate
> hardware receive and transmit queue for each core and configure the
> IXGBE to inspect the port number in each incoming packet header, place
> the packet on the queue dedicated to the associated memcached's core,
> and deliver the receive interrupt to that core." and the background of
> this configuration is that each memcached is pinned to a separate core
> and has its own UDP port. It seems that IXGBE's driver can detect UDP
> packets according to their port numbers and put these packets into
> corresponding receive queues in the hardware, is this achieved by
> configuring RSS in IXGBE? If it is, I am wondering whether bnx2
> supports RSS and whether it can configure in the same way.
> 
> I appreciate any help for this.

You're confusing RSS (flow hashing) with flow steering.  These are both
explained in Documentation/network/scaling.txt.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2012-03-04  0:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 21:25 How do I know my driver support RSS? Yuehai Xu
2012-03-04  0:10 ` Ben Hutchings [this message]
2012-03-04  4:30   ` Yuehai Xu
2012-03-04 22:23     ` Ben Hutchings

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=1330819855.8460.291.camel@deadeye \
    --to=bhutchings@solarflare.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sbw@mit.edu \
    --cc=yhxu@wayne.edu \
    --cc=yuehaixu@gmail.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 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).