linux-kernel - Re: regarding generic AIO, async syscalls precedent + some benchmarks by lighttpd

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] [day] [month] [year] [list]

Message-ID: <45C6D2C1.5010103@xman.org>
Date:	Sun, 04 Feb 2007 22:46:25 -0800
From:	Christopher Smith <x@...n.org>
To:	Davide Libenzi <davidel@...ilserver.org>
CC:	bert hubert <bert.hubert@...herlabs.nl>,
	Zach Brown <zach.brown@...cle.com>,
	Benjamin LaHaise <bcrl@...ck.org>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-aio@...ck.org, Suparna Bhattacharya <suparna@...ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: regarding generic AIO, async syscalls precedent + some benchmarks
 by lighttpd

Davide Libenzi wrote:
> Yes, that is some very interesting data IMO. I did not bench the GUASI 
> (userspace async thread library) against AIO, but those numbers show that a 
> *userspace* async syscall wrapper interface performs in the ballpark of AIO.
> This leads to some hope about the ability to effectively deploy the kernel 
> generic async AIO (being it fibril or kthreads based) as low-impact async 
> provider for basically anything.
>   

SGI's kaio patch to linux kind of went that route (using kthreads) for 
non-SCSI async IO. It wasn't a bad way to go, but at least for 
disk-based access they achieved much better results when they could go 
right to the hardware.

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