netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next] net: use indirect call wrappers for skb_copy_datagram_iter()
Date: Wed, 25 Mar 2020 17:00:02 +0100	[thread overview]
Message-ID: <2b5f096a143f4dea9c9a2896913d8ca79688b00f.camel@redhat.com> (raw)
In-Reply-To: <CA+FuTSdO_WBhrRj5PNdXppywDNkMKJ4hLry+3oSvy8mavnxw0g@mail.gmail.com>

On Wed, 2020-03-25 at 10:55 -0400, Willem de Bruijn wrote:
> On the UDP front this reminded me of another indirect function call
> without indirect call wrapper: getfrag in __ip_append_data.
> 
> That is called for each datagram once per linear + once per page. That
> said, the noise in my quick RR test was too great to measure any
> benefit from the following. 

Why an RR test ?

I think you should be able to measure some raw tput improvement with
large UDP GSO write towards a blackhole dst/or dropping ingress pkts
with XDP (just to be sure the bottle-neck is on the sender side).

> Paolo, did you happen to also look at that
> when introducing the indirect callers? Seems like it won't hurt to
> add.

Nope, sorry I haven't experimented that.

For the record, I have 2 others item on my list, I hope to have time to
process some day: the ingress dst->input and the default ->enqueue  and
->dequeue

Cheers,

Paolo

p.s. feel free to move this on a different thread, as it fit you better


  reply	other threads:[~2020-03-25 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  2:23 [PATCH net-next] net: use indirect call wrappers for skb_copy_datagram_iter() Eric Dumazet
2020-03-25  4:22 ` Eric Dumazet
2020-03-25 11:52 ` Paolo Abeni
2020-03-25 14:55   ` Willem de Bruijn
2020-03-25 16:00     ` Paolo Abeni [this message]
2020-03-25 16:07       ` Eric Dumazet
2020-03-25 16:24         ` Paolo Abeni
     [not found]           ` <CANn89iKotU9Tkd6KBgyicHFV72K9gZ+eeKwkPU097=gZZYCjrA@mail.gmail.com>
2020-03-25 16:46             ` Eric Dumazet
2020-03-25 20:58       ` Willem de Bruijn
2020-03-25 15:14   ` Eric Dumazet
2020-03-25 18:31 ` 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=2b5f096a143f4dea9c9a2896913d8ca79688b00f.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemdebruijn.kernel@gmail.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).