public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: target-devel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] vhost cleanups and separate module
Date: Tue, 07 May 2013 14:13:44 +0930	[thread overview]
Message-ID: <87zjw7o0vz.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130506091911.GB10601@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Mon, May 06, 2013 at 03:41:36PM +0930, Rusty Russell wrote:
>> Asias He <asias@redhat.com> writes:
>> > Asias He (3):
>> >   vhost: Remove vhost_enable_zcopy in vhost.h
>> >   vhost: Move VHOST_NET_FEATURES to net.c
>> >   vhost: Make vhost a separate module
>> 
>> I like these cleanups, MST pleasee apply.
>
> Absolutely. Except it's 3.11 material and I can only
> usefully create a -next branch once -rc1 is out.
>
>> I have some other cleanups which are on hold for the moment pending
>> MST's vhost_net simplification.  MST, how's that going?
>
> Not too well. The array of status bytes which was designed to complete
> packets in order turns out to be a very efficient datastructure:
>
> It gives us a way to signal completions that is completely lockless for
> multiple completers, and using the producer/consumer model saves extra
> scans for the common case.
>
> Overall I can save some memory and clean up some code but can't get rid
> of the producer/consumer idices (currently named upend/done indices)
> which is what you asked me to do.
> Your cleanups basically don't work with zcopy because they
> ignore the upend/done indices?
> Would you like to post them, noting they only work with zcopy off, and
> we'll look for a way to apply them, together?

Not quite; it's just that I don't understand that code.  It seemed to be
achieving something (ordered completion) which was entirely unnecessary,
so I went on with other things while you removed it.  Now that's not
possible, I'll revisit.

AFAICT we should always do zero copy.  Though I do wonder if we should
use a dedicated hook to get an skb into the tun driver and generate it
ourselves, rather than going sg -> iov -> skb.

Cheers,
Rusty.

  reply	other threads:[~2013-05-07  4:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  5:34 [PATCH 0/3] vhost cleanups and separate module Asias He
2013-05-03  5:34 ` [PATCH 1/3] vhost: Remove vhost_enable_zcopy in vhost.h Asias He
2013-05-03  5:34 ` [PATCH 2/3] vhost: Move VHOST_NET_FEATURES to net.c Asias He
2013-05-03  5:34 ` [PATCH 3/3] vhost: Make vhost a separate module Asias He
2013-05-06  6:11 ` [PATCH 0/3] vhost cleanups and " Rusty Russell
2013-05-06  8:15   ` Asias He
2013-05-06  9:19   ` Michael S. Tsirkin
2013-05-07  4:43     ` Rusty Russell [this message]
2013-05-07 12:44       ` Michael S. Tsirkin
2013-05-13  1:05         ` Rusty Russell
2013-05-13  3:39         ` 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=87zjw7o0vz.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=target-devel@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