[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130412002252.GD11956@mtj.dyndns.org>
Date: Thu, 11 Apr 2013 17:22:52 -0700
From: Tejun Heo <tj@...nel.org>
To: Mikulas Patocka <mpatocka@...hat.com>
Cc: Vivek Goyal <vgoyal@...hat.com>, Jens Axboe <axboe@...nel.dk>,
Mike Snitzer <snitzer@...hat.com>,
Milan Broz <gmazyland@...il.com>, dm-devel@...hat.com,
Andi Kleen <andi@...stfloor.org>, dm-crypt@...ut.de,
linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Christian Schmidt <schmidt@...add.de>,
"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 11, 2013 at 08:06:10PM -0400, Mikulas Patocka wrote:
> All that I can tell you is that adding an empty atomic operation
> "cmpxchg(&bio->bi_css->refcnt, bio->bi_css->refcnt, bio->bi_css->refcnt);"
> to bio_clone_context and bio_disassociate_task increases the time to run a
> benchmark from 23 to 40 seconds.
Right, linear target on ramdisk, very realistic, and you know what,
hell with dm, let's just hand code everything into submit_bio(). I'm
sure it will speed up your test case significantly.
If this actually matters, improve it in *sane* way. Make the refcnts
per-cpu and not use atomic ops. In fact, we already have proposed
implementation of percpu refcnt which is being used by aio restructure
patches and likely to be included in some form. It's not quite ready
yet, so please work on something useful like that instead of
continuing this non-sense.
--
tejun
--
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