[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130522185014.GA17423@redhat.com>
Date: Wed, 22 May 2013 14:50:14 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: Tejun Heo <tj@...nel.org>
Cc: Jens Axboe <axboe@...nel.dk>, dm-crypt@...ut.de,
Christian Schmidt <schmidt@...add.de>,
linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>, dm-devel@...hat.com,
Andi Kleen <andi@...stfloor.org>,
Mikulas Patocka <mpatocka@...hat.com>,
Vivek Goyal <vgoyal@...hat.com>,
Milan Broz <gmazyland@...il.com>,
"Alasdair G. Kergon" <agk@...hat.com>
Subject: Re: [PATCH v2] make dm and dm-crypt forward cgroup context (was:
dm-crypt parallelization patches)
On Thu, Apr 18 2013 at 1:03pm -0400,
Tejun Heo <tj@...nel.org> wrote:
> Hello, Mike.
>
> On Thu, Apr 18, 2013 at 12:47:42PM -0400, Mike Snitzer wrote:
> > I see you nack and raise you with: please reconsider in the near term.
>
> The thing is that percpu-refcnting is already in mostly ready-form, so
> unless this dm series is planned to be merged for v3.10-rc1, I don't
> see the need for a separate near term solution. Mikulas can just do
> the normal refcnting and cgroup will most likely adopt per-cpu ref
> anyway once percpu-refcnting is in, so it should all fall in places
> pretty quickly. For devel / testing / whatever, Mikulas can surely
> turn off cgroup, right?
Hey Tejun,
Was wondering: how is percpu-refcounting coming along? Do you have a
pointer to the code that can be pulled in for use by Mikulas' dm-crypt
changes?
Would be nice to get this stuff sorted out for the 3.11 merge window.
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists