From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.osdl.org
Subject: Re: INDIRECT and NEXT
Date: Fri, 23 Oct 2009 19:50:31 +1030 [thread overview]
Message-ID: <200910231950.31241.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20091023063648.GC10821@redhat.com>
On Fri, 23 Oct 2009 05:06:48 pm Michael S. Tsirkin wrote:
> On Fri, Oct 23, 2009 at 02:01:23PM +1030, Rusty Russell wrote:
> > Also, we have a limitation that you can't have more descriptors than the ring
> > size, even with indirect, due to overzealous checks...
>
> Yes ... so I wonder: do we want to fix all this and add a feature bit,
> or wait until some guest actually wants to use such descriptors?
Yes, we wait until someone wants it. Then (1) we have a test case, and
(2) we can make sure we don't do those (bogus, frankly) >= ringsize checks.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-10-23 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091004143734.GB17578@redhat.com>
2009-10-19 2:34 ` INDIRECT and NEXT Rusty Russell
2009-10-22 9:37 ` Michael S. Tsirkin
2009-10-23 3:31 ` Rusty Russell
2009-10-23 6:36 ` Michael S. Tsirkin
2009-10-23 9:20 ` Rusty Russell [this message]
2009-10-23 9:30 ` Michael S. Tsirkin
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=200910231950.31241.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=mst@redhat.com \
--cc=virtualization@lists.osdl.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.