From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Asias He <asias.hejun@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm tools: Process virito blk requests in separate thread
Date: Thu, 01 Dec 2011 10:58:37 +0200 [thread overview]
Message-ID: <1322729917.3702.10.camel@lappy> (raw)
In-Reply-To: <alpine.LFD.2.02.1112011048010.4549@tux.localdomain>
On Thu, 2011-12-01 at 10:48 +0200, Pekka Enberg wrote:
> On Wed, 30 Nov 2011, Asias He wrote:
> >>> In virtio net's notify_vq(), we simply signal the tx/rx handle thread
> >>> and return.
> >>
> >> Why not use the threadpool?
> >
> > No.
>
> Sasha?
I was looking into the concept of adding 'dedicated' threads to the
threadpool, since when the threadpool was added originally one of the
purposes was to have all worker threads in a single place.
This way we could still have threads in one place, which would make it
easier to control all of them but still won't hurt performance of those
threads.
We can merge this patch, and I'll do the dedicated thread patch on top
of it.
--
Sasha.
next prev parent reply other threads:[~2011-12-01 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:28 [PATCH] kvm tools: Process virito blk requests in separate thread Asias He
2011-11-29 14:36 ` Sasha Levin
2011-11-30 7:21 ` Asias He
2011-12-01 8:48 ` Pekka Enberg
2011-12-01 8:58 ` Sasha Levin [this message]
2011-12-01 10:45 ` Pekka Enberg
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 15:40 Asias He
2012-06-04 15:48 ` Cyrill Gorcunov
2012-06-05 0:47 ` Asias He
2012-06-05 6:10 ` Cyrill Gorcunov
2012-06-04 16:07 ` Sasha Levin
2012-06-05 1:03 ` Asias He
2012-06-05 8:14 ` Pekka Enberg
2012-06-06 12:35 ` Paolo Bonzini
2012-06-07 1:38 ` Asias He
2012-06-07 8:47 ` Paolo Bonzini
2012-06-08 3:30 ` Asias He
2012-06-05 8:15 ` Pekka Enberg
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=1322729917.3702.10.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@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 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).