From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3] virtio-serial-bus: use bh for unthrottling
Date: Mon, 2 May 2011 12:51:12 +0530 [thread overview]
Message-ID: <20110502072112.GF8308@amit-x200.redhat.com> (raw)
In-Reply-To: <20110430082342.GB16190@amber.local>
On (Sat) 30 Apr 2011 [11:23:42], Alon Levy wrote:
> On Fri, Apr 29, 2011 at 06:26:49PM +0530, Amit Shah wrote:
> > On (Fri) 29 Apr 2011 [14:25:06], Alon Levy wrote:
> > > Instead of calling flush_queued_data when unthrottling, schedule
> > > a bh. That way we can return immediately to the caller, and the
> > > flush uses the same call path as a have_data for callbackee.
> > >
> > > No migration change is required because bh are called from vm_stop.
> >
> > No sign-off?
> >
> > The initial tests look good, no fireworks yet.
> >
> > Amit
>
> Can I reply with a sign off?
>
> Signed-off-by: Alon Levy <alevy@redhat.com>
Yes, this is fine.
Amit
prev parent reply other threads:[~2011-05-02 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 11:25 [Qemu-devel] [PATCHv3] virtio-serial-bus: use bh for unthrottling Alon Levy
2011-04-29 11:35 ` Amit Shah
2011-04-29 12:56 ` Amit Shah
2011-04-30 8:23 ` Alon Levy
2011-05-02 7:21 ` Amit Shah [this message]
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=20110502072112.GF8308@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).