From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jon Zhou <Jon.Zhou@jdsu.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: RPS runs with multiqueue NIC
Date: Tue, 22 Feb 2011 06:46:03 +0100 [thread overview]
Message-ID: <1298353563.3360.6.camel@edumazet-laptop> (raw)
In-Reply-To: <4A6A2125329CFD4D8CC40C9E8ABCAB9F24D3DE6CC5@MILEXCH2.ds.jdsu.net>
Le lundi 21 février 2011 à 19:07 -0800, Jon Zhou a écrit :
> Hi
>
> What will happen if RPS runs on kernel 2.6.36.4 machine where a multiqueue NIC intel x520 installed
> Will it decrease or improve performance?
It depends on the workload.
For typical TCP flows, hardware multiqueue is generally better,
especially if the NIC supports the ethtool -X command (so that you can
tune effective number of cpus dedicated to the softirq processing).
Packet are delivered directly to the CPU target, without taking an extra
IPI.
For UDP workloads, adding RPS might be a win, because many NIC dont take
into account ports numbers in their hash computation, while
net/core/dev.c hash function does. If you receive trafic coming from a
single remote machine, RPS helps to spread flows between several cpus.
prev parent reply other threads:[~2011-02-22 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 3:07 RPS runs with multiqueue NIC Jon Zhou
2011-02-22 5:46 ` Eric Dumazet [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=1298353563.3360.6.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=Jon.Zhou@jdsu.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