linux-kernel - Re: [patch 05/11] syslets: core code

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: <20070214211231.GA18326@elte.hu>
Date:	Wed, 14 Feb 2007 22:12:31 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@....com.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ulrich Drepper <drepper@...hat.com>,
	Zach Brown <zach.brown@...cle.com>,
	Evgeniy Polyakov <johnpol@....mipt.ru>,
	"David S. Miller" <davem@...emloft.net>,
	Benjamin LaHaise <bcrl@...ck.org>,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Davide Libenzi <davidel@...ilserver.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 05/11] syslets: core code


* Ingo Molnar <mingo@...e.hu> wrote:

> * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> > And the whole "lock things down in memory" approach is bad. It's 
> > doing expensive things like mlock(), making the overhead for 
> > _single_ system calls much more expensive. [...]
> 
> hm, there must be some misunderstanding here. That mlock is /only/ 
> once per the lifetime of the whole 'head' - i.e. per 
> sys_async_register(). (And you can even forget i ever did it - it's 5 
> lines of code to turn the completion ring into a swappable entity.)
> 
> never does any MMU trick ever enter the picture during the whole 
> operation of this thing, and that's very much intentional.

to stress it: never does any mlocking or other lockdown happen of any 
syslet atom - it is /only/ the completion ring of syslet pointers that i 
made mlocked - but even that can be made generic memory no problem.

It's all about asynchronous system calls, and if you want you can have a 
terabyte of syslets in user memory, half of it swapped out. They have 
absolutely zero kernel context attached to them in the 'cached case' (be 
that locked memory or some other kernel resource).

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