| 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: <1200995361-24001-1-git-send-email-jens.axboe@oracle.com> Date: Tue, 22 Jan 2008 10:49:15 +0100 From: Jens Axboe <jens.axboe@...cle.com> To: linux-kernel@...r.kernel.org Cc: knikanth@...ell.com Subject: [PATCH 0/6] IO context sharing Hi, Today io contexts are per-process and define the (surprise) io context of that process. In some situations it would be handy if several processes share an IO context. With syslets it's especially crucial that the threads working on behalf of the parent process are seen as the same IO context. That goes from both a fairness and performance point of view, since IO schedulers like AS and CFQ base decisions on what the IO context state is. This patchset adds support for processes sharing a single io context and also adds a CLONE_IO flag to denote sharing of IO context. In the block git repo here's a syslet-share branch that merges these patches with the latest syslet patches posted from Zach and sets CLONE_IO for syslet threads. The result is that performance of AS and CFQ is as good as it would have been had a single process issued the IO async through libaio. This work was originally started by Nikanth Karthikesan <knikanth@...ell.com>, but then later completely reworked by me. The patches are against latest -git. -- 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