| 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
| ||
|
Date: Tue, 22 Apr 2008 16:54:18 +0200 From: Jens Axboe <jens.axboe@...cle.com> To: Hirokazu Takahashi <taka@...inux.co.jp> Cc: agk@...rceware.org, dm-devel@...hat.com, linux-kernel@...r.kernel.org Subject: Re: [RFC][PATCH 0/10] I/O context inheritance On Tue, Apr 22 2008, Hirokazu Takahashi wrote: > Hi, > > Sorry, these patches are for linux-2.6.25. > > > This series of patches make the block I/O layer and the I/O schedulers > > be able to determine the right io_context of every I/O. > > > > The current implementation of the block I/O layer and the I/O schedulers > > assume that the current process is the one which issued the given I/O, > > then use the io_context of this process to control the I/O. > > But this assumption isn't quite right because several kernel threads > > will handle I/O requests on behalf of the processes which originated them. > > This often happens when you want to use device mapper modules. > > > > The patches make every bio has a pointer to an io_context, which will > > be set when it is allocated or cloned. So it makes it possible to find > > the right io_context from any bio at any place. > > > > I'm waiting for your comments. Can you give a brief summary of what you need this stuff for? -- Jens Axboe -- 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