From: Tejun Heo <tj@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Nate Custer <nate@cpanel.net>, Jens Axboe <axboe@kernel.dk>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFT PATCH] blkio: alloc per cpu data from worker thread context( Re: kvm deadlock)
Date: Tue, 20 Dec 2011 12:45:22 -0800 [thread overview]
Message-ID: <20111220204522.GI10752@google.com> (raw)
In-Reply-To: <20111220145024.GA16946@redhat.com>
Hello,
On Tue, Dec 20, 2011 at 09:50:24AM -0500, Vivek Goyal wrote:
> So IIUC, existing mempool implementation is not directly usable for my
> requirement and I need to write some code of my own for the caching
> layer which always allocates objects from reserve and fills in the
> pool asynchronously with the help of a worker thread.
I've been looking at it and don't think allowing percpu allocator to
be called from no io path is a good idea. The on-demand area filling
is tied into vmalloc area management which in turn is tied to arch
page table code and I really want to avoid pre-allocating full chunk -
it can be huge. I'm trying to extend mempool to cover percpu areas,
so please wait a bit.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-12-20 20:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54FC5923-2123-4BDD-A506-EA57DCE0C1F6@cpanel.net>
[not found] ` <20111214122511.GD18317@amt.cnet>
2011-12-14 13:43 ` kvm deadlock Avi Kivity
2011-12-14 14:00 ` Marcelo Tosatti
2011-12-14 14:02 ` Avi Kivity
2011-12-14 14:06 ` Marcelo Tosatti
2011-12-14 14:17 ` Nate Custer
2011-12-14 14:20 ` Marcelo Tosatti
2011-12-14 14:28 ` Avi Kivity
2011-12-14 14:27 ` Avi Kivity
2011-12-14 16:03 ` Jens Axboe
2011-12-14 17:03 ` Vivek Goyal
2011-12-14 17:09 ` Jens Axboe
2011-12-14 17:22 ` Vivek Goyal
2011-12-14 18:16 ` Tejun Heo
2011-12-14 18:41 ` Vivek Goyal
2011-12-14 23:06 ` Vivek Goyal
2011-12-15 19:47 ` [RFT PATCH] blkio: alloc per cpu data from worker thread context( Re: kvm deadlock) Vivek Goyal
[not found] ` <E73DB38E-AFC5-445D-9E76-DE599B36A814@cpanel.net>
2011-12-16 20:29 ` Vivek Goyal
2011-12-18 21:25 ` Nate Custer
2011-12-19 13:40 ` Vivek Goyal
2011-12-19 17:27 ` Vivek Goyal
2011-12-19 17:35 ` Tejun Heo
2011-12-19 18:27 ` Vivek Goyal
2011-12-19 22:56 ` Tejun Heo
2011-12-20 14:50 ` Vivek Goyal
2011-12-20 20:45 ` Tejun Heo [this message]
2011-12-20 12:49 ` Jens Axboe
2011-12-16 18:47 Nate Custer
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=20111220204522.GI10752@google.com \
--to=tj@kernel.org \
--cc=avi@redhat.com \
--cc=axboe@kernel.dk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nate@cpanel.net \
--cc=vgoyal@redhat.com \
/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).