From: Eric Dumazet <eric.dumazet@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v2 3/3] udp: keep the sk_receive_queue held when splicing
Date: Tue, 16 May 2017 07:12:26 -0700 [thread overview]
Message-ID: <1494943946.6465.5.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <35e3fc420159a14392b9a2f501f76cc6eb59ba0f.1494881617.git.pabeni@redhat.com>
On Tue, 2017-05-16 at 11:20 +0200, Paolo Abeni wrote:
> On packet reception, when we are forced to splice the
> sk_receive_queue, we can keep the related lock held, so
> that we can avoid re-acquiring it, if fwd memory
> scheduling is required.
>
> v1 -> v2:
> the rx_queue_lock_held param in udp_rmem_release() is
> now a bool
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2017-05-16 14:12 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 [this message]
2017-05-16 19:41 ` [PATCH net-next v2 0/3] udp: scalability improvements David Miller
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=1494943946.6465.5.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=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 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.