linux-kernel - Re: [PATCH 0/6] IO context sharing

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080122182121.GX6258@kernel.dk>
Date:	Tue, 22 Jan 2008 19:21:21 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	linux-kernel@...r.kernel.org, knikanth@...ell.com
Subject: Re: [PATCH 0/6] IO context sharing

On Tue, Jan 22 2008, Peter Zijlstra wrote:
> 
> On Tue, 2008-01-22 at 10:49 +0100, Jens Axboe wrote:
> > 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.
> 
> Are you planning on extending this to a hierarchical CFQ for cgroups, or
> just giving the IO context to a cgroup?

Not sure what extra extensions it would need on the IO side. As long as
the other side makes sure to group its processes by sharing IO context,
then CFQ will treat that as a single entity.

-- 
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/