linux-kernel - Re: [patch] aio: remove aio-max-nr and instead use the memlock rlimit to limit the number of pages pinned for the aio completion ring

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: <20090309203624.GA2812@shareable.org>
Date:	Mon, 9 Mar 2009 20:36:24 +0000
From:	Jamie Lokier <jamie@...reable.org>
To:	Avi Kivity <avi@...hat.com>
Cc:	Jeff Moyer <jmoyer@...hat.com>, linux-aio <linux-aio@...ck.org>,
	zach.brown@...cle.com, bcrl@...ck.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] aio: remove aio-max-nr and instead use the memlock rlimit to limit the number of pages pinned for the aio completion ring

Avi Kivity wrote:
> Or you could queue the completions somewhere, and only copy them to
> user memory when io_getevents() is called.  I think the plan was
> once to allow events to be consumed opportunistically even without
> io_getevents(), though.

Isn't that integrated (or to be integrated) with the vring buffer
thingy used by virtio?

If not, should it be?

> Sorry, I didn't actually take a look at the patches.  I only reacted to 
> the description - I am allergic to pinned memory.

While we're at it I'm allergic to fixed size ring buffers :-)

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