From: Rusty Russell <rusty@rustcorp.com.au>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Jan-Bernd Themann <THEMANN@de.ibm.com>
Subject: Re: [RFC v1] virtio: add virtio-over-PCI driver
Date: Wed, 18 Feb 2009 17:13:03 +1030 [thread overview]
Message-ID: <200902181713.03820.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090217222425.GA18801@ovro.caltech.edu>
On Wednesday 18 February 2009 08:54:25 Ira Snyder wrote:
> This adds support to Linux for using virtio between two computers linked by
> a PCI interface. This allows the use of virtio_net to create a familiar,
> fast interface for communication. It should be possible to use other virtio
> devices in the future, but this has not been tested.
Hi Ira,
It's only first glance, but this looks sane. Two things on first note:
don't restrict yourself to 32 feature bits (only PCI does this, and they're
going to have to hack when we reach feature 32).
Secondly:
> +You will notice that the algorithm has no way of handling chains that are
> +not exactly the same on the host and guest system. Without setting any of
> +the fancier virtio_net features, this is the case.
Hmm, I think we can do slightly better than this.
How about prepending a 4 byte length on the host buffers? Allows host to
specify length (for host->guest), and guest writes it to allow truncated
buffers on guest->host.
That won't allow you to transfer *more* than one buffersize to the host, but
you could use a different method (perhaps the 4 bytes indicates the *total*
length?).
Do 4-byte DMA's suck for some reason?
Cheers,
Rusty.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
"Jan-Bernd Themann" <THEMANN@de.ibm.com>,
netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [RFC v1] virtio: add virtio-over-PCI driver
Date: Wed, 18 Feb 2009 17:13:03 +1030 [thread overview]
Message-ID: <200902181713.03820.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090217222425.GA18801@ovro.caltech.edu>
On Wednesday 18 February 2009 08:54:25 Ira Snyder wrote:
> This adds support to Linux for using virtio between two computers linked by
> a PCI interface. This allows the use of virtio_net to create a familiar,
> fast interface for communication. It should be possible to use other virtio
> devices in the future, but this has not been tested.
Hi Ira,
It's only first glance, but this looks sane. Two things on first note:
don't restrict yourself to 32 feature bits (only PCI does this, and they're
going to have to hack when we reach feature 32).
Secondly:
> +You will notice that the algorithm has no way of handling chains that are
> +not exactly the same on the host and guest system. Without setting any of
> +the fancier virtio_net features, this is the case.
Hmm, I think we can do slightly better than this.
How about prepending a 4 byte length on the host buffers? Allows host to
specify length (for host->guest), and guest writes it to allow truncated
buffers on guest->host.
That won't allow you to transfer *more* than one buffersize to the host, but
you could use a different method (perhaps the 4 bytes indicates the *total*
length?).
Do 4-byte DMA's suck for some reason?
Cheers,
Rusty.
next prev parent reply other threads:[~2009-02-18 6:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 22:24 [RFC v1] virtio: add virtio-over-PCI driver Ira Snyder
2009-02-17 22:24 ` Ira Snyder
2009-02-18 6:43 ` Rusty Russell [this message]
2009-02-18 6:43 ` Rusty Russell
2009-02-18 16:38 ` Ira Snyder
2009-02-18 16:38 ` Ira Snyder
2009-02-19 11:18 ` Rusty Russell
2009-02-19 11:18 ` Rusty Russell
2009-02-19 16:49 ` Ira Snyder
2009-02-19 16:49 ` Ira Snyder
2009-02-18 16:47 ` Kumar Gala
2009-02-18 16:47 ` Kumar Gala
2009-02-19 6:13 ` Zang Roy-R61911
2009-02-19 6:13 ` Zang Roy-R61911
2009-02-19 16:51 ` Kumar Gala
2009-02-19 16:51 ` Kumar Gala
2009-02-19 17:03 ` Ira Snyder
2009-02-19 17:03 ` Ira Snyder
2009-02-20 3:44 ` Zang Roy-R61911
2009-02-20 3:44 ` Zang Roy-R61911
2009-02-19 6:10 ` Zang Roy-R61911
2009-02-19 6:10 ` Zang Roy-R61911
2009-02-19 16:14 ` Ira Snyder
2009-02-19 16:14 ` Ira Snyder
2009-02-20 3:37 ` Zang Roy-R61911
2009-02-20 3:37 ` Zang Roy-R61911
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=200902181713.03820.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=THEMANN@de.ibm.com \
--cc=arnd@arndb.de \
--cc=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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 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.