netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: willemb@google.com
Cc: netdev@vger.kernel.org, edumazet@google.com, therbert@google.com
Subject: Re: [PATCH net-next] rps: overflow prevention for saturated cpus
Date: Fri, 07 Dec 2012 14:20:04 -0500 (EST)	[thread overview]
Message-ID: <20121207.142004.1330913822593924898.davem@davemloft.net> (raw)
In-Reply-To: <1354826194-9289-1-git-send-email-willemb@google.com>

From: Willem de Bruijn <willemb@google.com>
Date: Thu,  6 Dec 2012 15:36:34 -0500

> This patch maintains flow affinity in normal conditions, but
> trades it for throughput when a cpu becomes saturated. Then, packets
> destined to that cpu (only) are redirected to the lightest loaded cpu
> in the rxqueue's rps_map. This breaks flow affinity under high load
> for some flows, in favor of processing packets up to the capacity
> of the complete rps_map cpuset in all circumstances.

We specifically built-in very strict checks to make sure we never
deliver packets out-of-order.  Those mechanisms must be used and
enforced in any change of this nature.

  parent reply	other threads:[~2012-12-07 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 20:36 [PATCH net-next] rps: overflow prevention for saturated cpus Willem de Bruijn
2012-12-06 22:25 ` Rick Jones
2012-12-06 23:04   ` Willem de Bruijn
2012-12-06 23:45     ` Rick Jones
2012-12-07 16:04       ` Willem de Bruijn
2012-12-07 14:51 ` Ben Hutchings
2012-12-07 16:41   ` Willem de Bruijn
2012-12-07 19:20 ` David Miller [this message]
2012-12-10 20:09   ` Willem de Bruijn

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=20121207.142004.1330913822593924898.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.com \
    --cc=willemb@google.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).