| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20140731190041.GA1967@htj.dyndns.org> Date: Thu, 31 Jul 2014 15:00:41 -0400 From: Tejun Heo <tj@...nel.org> To: linux-kernel@...r.kernel.org Cc: Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <axboe@...nel.dk>, Vivek Goyal <vgoyal@...hat.com> Subject: Re: [PATCH percpu/for-3.17 1/2] percpu: implement percpu_pool On Fri, Jul 18, 2014 at 04:08:04PM -0400, Tejun Heo wrote: > Hello, > > So, I have another case where percpu allocation needs to be performed > from an atomic context (also on the IO path), so I wrote up a simple > percpu alloc cache which is filled asynchronously and replaced > blk-throttle's custom implementation with it. > > I still think it's quite unlikely that we implement atomic allocation > directly in the percpu allocator; however, even if that happens > eventually, having percpu_pool instead of multiple custom mechanisms > scattered around the kernel should make it a lot easier to transition > to that. > > Thanks. > ------ 8< ------ > From eaaca4e64d3cce54d2b7ac5e4d5fb207290cc48f Mon Sep 17 00:00:00 2001 > From: Tejun Heo <tj@...nel.org> > Date: Fri, 18 Jul 2014 16:07:14 -0400 > Subject: [PATCH 1/2] percpu: implement percpu_pool Applied the first patch to percpu/for-3.17. Jens, how should I route the second patch? Thanks. -- 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