linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next V2 2/3] vhost_net: tx batching
Date: Tue, 3 Jan 2017 13:16:30 +0000	[thread overview]
Message-ID: <20170103131630.GB14707@stefanha-x1.localdomain> (raw)
In-Reply-To: <1482912571-3157-3-git-send-email-jasowang@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

On Wed, Dec 28, 2016 at 04:09:30PM +0800, Jason Wang wrote:
> This patch tries to utilize tuntap rx batching by peeking the tx
> virtqueue during transmission, if there's more available buffers in
> the virtqueue, set MSG_MORE flag for a hint for backend (e.g tuntap)
> to batch the packets.
> 
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
>  drivers/vhost/net.c | 23 ++++++++++++++++++++---
>  1 file changed, 20 insertions(+), 3 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-01-03 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28  8:09 [PATCH net-next V2 0/3] vhost net tx batching Jason Wang
2016-12-28  8:09 ` [PATCH net-next V2 1/3] vhost: better detection of available buffers Jason Wang
2017-01-03 13:08   ` Stefan Hajnoczi
2016-12-28  8:09 ` [PATCH net-next V2 2/3] vhost_net: tx batching Jason Wang
2017-01-03 13:16   ` Stefan Hajnoczi [this message]
2016-12-28  8:09 ` [PATCH net-next V2 3/3] tun: rx batching Jason Wang
2016-12-29 16:35   ` David Miller
2016-12-30  5:14     ` Jason Wang
2017-01-03 13:33   ` Stefan Hajnoczi
2017-01-04  3:03     ` Jason Wang
2017-01-05  9:27       ` Stefan Hajnoczi

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=20170103131630.GB14707@stefanha-x1.localdomain \
    --to=stefanha@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 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).