From: Jay Vosburgh <fubar@us.ibm.com>
To: rick.jones2@hp.com
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: small RPS cache for fragments?
Date: Mon, 06 Jun 2011 14:06:09 -0700 [thread overview]
Message-ID: <17839.1307394369@death> (raw)
In-Reply-To: <1307390721.8149.2763.camel@tardy>
Rick Jones <rick.jones2@hp.com> wrote:
>On Mon, 2011-06-06 at 12:22 -0700, David Miller wrote:
>> From: Rick Jones <rick.jones2@hp.com>
>> Date: Mon, 06 Jun 2011 10:08:52 -0700
>>
>> > Mode-rr bonding reorders TCP segments all the time.
>>
>> Oh well, then don't use this if you care about performance at all.
>> And therefore it's not even worth considering for our RPS fragment
>> cache.
>
>Heh - the (or at least a) reason people use mode-rr is to make a single
>(TCP) stream go faster :) Without buying the next-up NIC speed.
Right, the common use case for balance-rr (round robin) is to
maximize TCP throughput for one connection, over a set of whatever
network devices are available (or are cheap) by striping that connection
across multiple interfaces. The tcp_reordering sysctl is set to some
large value so that TCP will deal with the reordering as best it can.
Since TCP generally won't fragment, I don't see that the RPS
frag cache is going to matter for this usage anyway.
If somebody out there is using round robin for some UDP-based
application that doesn't care about packet ordering (but might create
fragmented datagrams), I've not heard about it.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2011-06-06 21:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 18:33 small RPS cache for fragments? David Miller
2011-05-17 20:02 ` Tom Herbert
2011-05-17 20:17 ` Rick Jones
2011-05-17 20:41 ` Rick Jones
2011-05-17 20:49 ` David Miller
2011-05-17 21:00 ` Eric Dumazet
2011-05-17 21:10 ` David Miller
2011-05-17 21:13 ` Rick Jones
2011-05-17 21:13 ` Ben Hutchings
2011-05-17 21:26 ` David Miller
2011-05-17 21:40 ` Rick Jones
2011-05-17 21:27 ` Eric Dumazet
2011-05-17 21:11 ` Rick Jones
2011-05-17 21:11 ` Ben Hutchings
2011-05-17 21:27 ` Tom Herbert
2011-05-17 21:28 ` David Miller
2011-05-17 23:59 ` Changli Gao
2011-05-18 6:37 ` David Miller
2011-05-17 20:14 ` Eric Dumazet
2011-05-17 20:47 ` David Miller
2011-05-17 21:44 ` Andi Kleen
2011-05-17 21:52 ` Eric Dumazet
2011-05-17 22:03 ` Andi Kleen
2011-05-17 21:44 ` David Miller
2011-05-17 21:48 ` Andi Kleen
2011-05-17 21:50 ` David Miller
2011-05-17 22:06 ` Andi Kleen
2011-05-17 22:42 ` Rick Jones
2011-05-24 20:01 ` David Miller
2011-05-24 21:38 ` Rick Jones
2011-06-04 20:29 ` David Miller
2011-06-06 17:08 ` Rick Jones
2011-06-06 17:15 ` Eric Dumazet
2011-06-06 18:06 ` Rick Jones
2011-06-06 19:23 ` David Miller
2011-06-06 19:22 ` David Miller
2011-06-06 20:05 ` Rick Jones
2011-06-06 21:06 ` Jay Vosburgh [this message]
2011-06-06 21:40 ` David Miller
2011-06-06 22:49 ` Chris Friesen
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=17839.1307394369@death \
--to=fubar@us.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 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.