From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] ethervirtio
Date: Tue, 2 Dec 2014 07:47:58 +0100 [thread overview]
Message-ID: <20141202074758.796e8383@zinc.9fans.fr> (raw)
In-Reply-To: <a391d8b1377d2c50ac7c84facaf48c47@sigma.offblast.org>
> david (0intro) tested the driver on GCE a few months ago, and
> reported that it did *not* work. i don't recall what exactly
> happened, but the virtio device in GCE seems to differ from qemu's.
I haven't tried for a while, since the debugging process is
a bit time consuming.
As far I remember, the virtqueue sizes read from the Virtio
common configuration structure were not correct (as reported
by the "legacy interface").
Rx/Tx/Control were something like 16384/81920/131136, while
the maximum queue size is 32768 according to the specification.
http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html
Setting Tx and Control queue size to more realistic values
seems to work, but then I couldn't get the interruptions to
work properly.
Something seems to be missing during the device initialization.
The original discussion thread was:
https://groups.google.com/forum/#!topic/golang-dev/Vb4fcGwg-dE
It includes links to the code and everything that's needed
to run Plan 9 on GCE (last email).
--
David du Colombier
next prev parent reply other threads:[~2014-12-02 6:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 4:01 mischief
2014-12-02 4:22 ` erik quanstrom
2014-12-02 4:28 ` erik quanstrom
2014-12-02 5:04 ` mischief
2014-12-02 5:11 ` erik quanstrom
2014-12-02 6:47 ` David du Colombier [this message]
2014-12-04 0:05 ` mischief
2014-12-04 0:33 ` mischief
2014-12-04 1:01 ` Skip Tavakkolian
2014-12-04 1:29 ` mischief
2014-12-04 6:40 ` Skip Tavakkolian
2014-12-04 7:23 ` David du Colombier
2014-12-04 12:52 ` hiro
2014-12-06 19:52 ` erik quanstrom
2014-12-06 23:56 ` David du Colombier
2014-12-07 1:21 ` mischief
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=20141202074758.796e8383@zinc.9fans.fr \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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).