From: David Miller <davem@davemloft.net>
To: pabeni@redhat.com
Cc: netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH net-next v2 0/3] udp: scalability improvements
Date: Tue, 16 May 2017 15:41:49 -0400 (EDT) [thread overview]
Message-ID: <20170516.154149.199666340821000197.davem@davemloft.net> (raw)
In-Reply-To: <cover.1494881617.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Tue, 16 May 2017 11:20:12 +0200
> This patch series implement an idea suggested by Eric Dumazet to
> reduce the contention of the udp sk_receive_queue lock when the socket is
> under flood.
Series applied, thanks a lot.
prev parent reply other threads:[~2017-05-16 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 9:20 [PATCH net-next v2 0/3] udp: scalability improvements Paolo Abeni
2017-05-16 9:20 ` [PATCH net-next v2 1/3] net/sock: factor out dequeue/peek with offset code Paolo Abeni
2017-05-17 2:46 ` [net-next,v2,1/3] " Andrei Vagin
2017-05-16 9:20 ` [PATCH net-next v2 2/3] udp: use a separate rx queue for packet reception Paolo Abeni
2017-05-16 9:20 ` [PATCH net-next v2 3/3] udp: keep the sk_receive_queue held when splicing Paolo Abeni
2017-05-16 14:12 ` Eric Dumazet
2017-05-16 19:41 ` David Miller [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=20170516.154149.199666340821000197.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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