All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Jason Wang <jasowang@redhat.com>,
	mst@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davem@davemloft.net
Cc: eric.dumazet@gmail.com, brouer@redhat.com
Subject: Re: [PATCH net-next V2] tun: introduce tx skb ring
Date: Wed, 15 Jun 2016 07:52:47 -0400	[thread overview]
Message-ID: <5761418F.2050407@mojatatu.com> (raw)
In-Reply-To: <1465979897-4445-1-git-send-email-jasowang@redhat.com>

On 16-06-15 04:38 AM, Jason Wang wrote:
> We used to queue tx packets in sk_receive_queue, this is less
> efficient since it requires spinlocks to synchronize between producer
> and consumer.
> 
> This patch tries to address this by:
> 
> - introduce a new mode which will be only enabled with IFF_TX_ARRAY
>    set and switch from sk_receive_queue to a fixed size of skb
>    array with 256 entries in this mode.
> - introduce a new proto_ops peek_len which was used for peeking the
>    skb length.
> - implement a tun version of peek_len for vhost_net to use and convert
>    vhost_net to use peek_len if possible.
> 
> Pktgen test shows about 18% improvement on guest receiving pps for small
> buffers:
> 
> Before: ~1220000pps
> After : ~1440000pps
> 

So this is more exercising the skb array improvements. For tun
it would be useful to see general performance numbers on user/kernel
crossing (i.e tun read/write).
If you have the cycles can you run such tests?

cheers,
jamal

  parent reply	other threads:[~2016-06-15 11:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  8:38 [PATCH net-next V2] tun: introduce tx skb ring Jason Wang
2016-06-15 10:34 ` kbuild test robot
2016-06-15 10:34 ` kbuild test robot
2016-06-15 11:52 ` Jamal Hadi Salim [this message]
2016-06-15 11:55   ` Jamal Hadi Salim
2016-06-16  7:08     ` Jason Wang
2016-06-15 11:55   ` Jamal Hadi Salim
2016-06-15 11:52 ` Jamal Hadi Salim
2016-06-17  0:01 ` David Miller
2016-06-17  0:01   ` David Miller
2016-06-17  0:41 ` Michael S. Tsirkin
2016-06-17  0:41 ` Michael S. Tsirkin
2016-06-17  7:22   ` Jason Wang
2016-06-17  7:22   ` Jason Wang
2016-06-22 18:18   ` Michael S. Tsirkin
2016-06-22 18:18     ` Michael S. Tsirkin
2016-06-23  5:14     ` Jason Wang
2016-06-23  5:14       ` Jason Wang
2016-06-28  7:09       ` Michael S. Tsirkin
2016-06-28  7:09         ` Michael S. Tsirkin
2016-06-30  1:50         ` Jason Wang
2016-06-30  1:50           ` Jason Wang
2016-06-15  8:38 Jason Wang

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=5761418F.2050407@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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 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.