From: Paolo Abeni <pabeni@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] udp: prefetch rmem_alloc in udp_queue_rcv_skb()
Date: Wed, 21 Jun 2017 18:07:37 +0200 [thread overview]
Message-ID: <1498061257.2799.15.camel@redhat.com> (raw)
In-Reply-To: <20170621.114155.502883498671476879.davem@davemloft.net>
On Wed, 2017-06-21 at 11:41 -0400, David Miller wrote:
> From: Paolo Abeni <pabeni@redhat.com>
> Date: Wed, 21 Jun 2017 10:24:40 +0200
>
> > On UDP packets processing, if the BH is the bottle-neck, it
> > always sees a cache miss while updating rmem_alloc; try to
> > avoid it prefetching the value as soon as we have the socket
> > available.
> >
> > Performances under flood with multiple NIC rx queues used are
> > unaffected, but when a single NIC rx queue is in use, this
> > gives ~10% performance improvement.
> >
> > Signed-off-by: Paolo Abeni <pabeni@redhat.com>
>
> Applied, but what about ipv6?
You are right, that was unintentionally left out. I'll do some tests
and send another patch for ipv6, too.
Thanks,
Paolo
prev parent reply other threads:[~2017-06-21 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 8:24 [PATCH net-next] udp: prefetch rmem_alloc in udp_queue_rcv_skb() Paolo Abeni
2017-06-21 15:41 ` David Miller
2017-06-21 16:07 ` Paolo Abeni [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=1498061257.2799.15.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).