From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Arnd Bergmann <arnd@arndb.de>,
virtualization@lists.linux-foundation.org
Subject: Re: virtio over PCI
Date: Wed, 3 Mar 2010 16:39:20 -0800 [thread overview]
Message-ID: <20100304003920.GA12707@ovro.caltech.edu> (raw)
In-Reply-To: <1267596588.7814.159.camel@concordia>
On Wed, Mar 03, 2010 at 05:09:48PM +1100, Michael Ellerman wrote:
> Hi guys,
>
> I was looking around at virtio over PCI stuff and noticed you had
> started some work on a driver. The last I can find via google is v2 from
> mid last year, is that as far as it got?
>
> http://lkml.org/lkml/2009/2/23/353
>
Yep, that is pretty much as far as I got. It was more-or-less rejected
because I hooked two instances of virtio-net together, rather than
having a proper backend and using virtio-net as the frontend.
I got started on writing a backend, which was never posted to LKML
because I never finished it. Feel free to take the code and use it to
start your own project. Note that vhost-net exists now, and is an
in-kernel backend for virtio-net. It *may* be possible to use this,
rather than writing a userspace backend as I started to do.
http://www.mmarray.org/~iws/virtio-phys/
I also got started with the alacrityvm project, developing a driver for
their virtualization framework. That project is nowhere near finished.
The virtualization folks basically told GHaskins (alacrityvm author)
that alacrityvm wouldn't ever make it to mainline Linux.
http://www.mmarray.org/~iws/vbus/
Unfortunately, I've been pulled onto other projects for the time being.
However, I'd really like to be able to use a virtio-over-PCI style
driver, rather than relying on my own custom (slow, unoptimized) network
driver (PCINet).
If you get something mostly working (and mostly agreed upon by the
virtualization guys), I will make the time to test it and get it cleaned
up. I've had 10+ people email me privately about this kind of driver
now. It is an area where Linux is sorely lacking.
I'm happy to provide any help I can, including testing on
MPC8349EA-based system. I would suggest talking to the virtualization
mailing list before you get too deep in the project. They sometimes have
good advice. I've added them to the CC list, so maybe they can comment.
https://lists.linux-foundation.org/mailman/listinfo/virtualization
Good luck, and let me know if I can help.
Ira
next parent reply other threads:[~2010-03-04 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267596588.7814.159.camel@concordia>
2010-03-04 0:39 ` Ira W. Snyder [this message]
2010-03-03 16:45 ` virtio over PCI Arnd Bergmann
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=20100304003920.GA12707@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=michael@ellerman.id.au \
--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.