From: Eric Dumazet <eric.dumazet@gmail.com>
To: Willem de Bruijn <willemb@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com
Subject: Re: [PATCH net-next] packet: packet fanout rollover during socket overload
Date: Wed, 13 Mar 2013 15:25:17 +0100 [thread overview]
Message-ID: <1363184717.13690.53.camel@edumazet-glaptop> (raw)
In-Reply-To: <1363102664-5174-1-git-send-email-willemb@google.com>
On Tue, 2013-03-12 at 11:37 -0400, Willem de Bruijn wrote:
> Minimize packet drop in a fanout group. If one socket is full,
> roll over packets to another from the group. The intended use is
> to maintain flow affinity during normal load using an rxhash or
> cpu fanout policy, while dispersing unexpected traffic storms that
> hit a single cpu, such as spoofed-source DoS flows. This mechanism
> breaks affinity for flows arriving at saturated sockets during
> those conditions.
>
> The patch adds a fanout policy ROLLOVER that rotates between sockets,
> filling each socket before moving to the next. It also adds a fanout
> flag ROLLOVER. If passed along with any other fanout policy, the
> primary policy is applied until the chosen socket is full. Then,
> rollover selects another socket, to delay packet drop until the
> entire system is saturated.
>
> Probing sockets is not free. Selecting the last used socket, as
> rollover does, is a greedy approach that maximizes chance of
> success, at the cost of extreme load imbalance. In practice, with
> sufficiently long queues to handle rate, sockets are drained in
> parallel and load balance looks uniform in `top`.
>
> To avoid contention, scales counters with number of sockets and
> accesses them lockfree. Values are bounds checked to ensure
> correctness. An alternative would be to use atomic rr_cur.
>
> Tested using an application with 9 threads pinned to CPUs, one socket
> per thread and sufficient busywork per packet operation to limits each
> thread to handling 32 Kpps. When sent 500 Kpps single UDP stream
> packets, a FANOUT_CPU setup processes 32 Kpps in total without this
> patch, 270 Kpps with the patch. Tested with read() and with a packet
> ring (V1).
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>
> ---
> include/linux/if_packet.h | 2 +
> net/packet/af_packet.c | 112 ++++++++++++++++++++++++++++++++++++----------
> 2 files changed, 90 insertions(+), 24 deletions(-)
> -static struct sock *fanout_demux_cpu(struct packet_fanout *f, struct sk_buff *skb, unsigned int num)
> +static unsigned int fanout_demux_rollover(struct packet_fanout *f,
> + struct sk_buff *skb,
> + unsigned int idx, unsigned int skip,
> + unsigned int num)
> {
> - unsigned int cpu = smp_processor_id();
> + unsigned int i, j;
>
> - return f->arr[cpu % num];
> + i = j = min(f->next[idx], (int) f->num_members - 1);
min_t(int, f->next[idx], f->num_members - 1);
BTW, num_members can be 0
You really should do
int members = ACCESS_ONCE(f->num_members) - 1;
if (members < 0)
return idx;
and only use members in your loop.
> + do {
> + if (i != skip && packet_rcv_has_room(pkt_sk(f->arr[i]), skb)) {
> + if (i != j)
> + f->next[idx] = i;
> + return i;
> + }
> + if (++i >= f->num_members)
> + i = 0;
> + } while (i != j && idx < f->num_members);
> +
> + return idx;
> +}
> +
next prev parent reply other threads:[~2013-03-13 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 14:55 [PATCH net-next] packet: packet fanout rollover during socket overload Willem de Bruijn
2013-03-12 15:37 ` Willem de Bruijn
2013-03-13 14:25 ` Eric Dumazet [this message]
2013-03-13 15:51 ` Willem de Bruijn
2013-03-13 8:44 ` David Miller
2013-03-13 8:45 ` David Miller
2013-03-13 16:13 ` Willem de Bruijn
2013-03-14 15:46 ` Eric Dumazet
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=1363184717.13690.53.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--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