linux-kernel - Re: aio is unlikely

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: <464E2098.8020900@cfl.rr.com>
Date:	Fri, 18 May 2007 17:54:32 -0400
From:	Phillip Susi <psusi@....rr.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Alex Volkov <avcp-lkmail@....net>, 'Jeff Garzik' <jeff@...zik.org>,
	'Linux Kernel Mailing List' <linux-kernel@...r.kernel.org>
Subject: Re: aio is unlikely

Andrew Morton wrote:
> Yes, if you agree with Jeff's original point.
> 
> But I don't, actually.  Sure, on some machines+workloads, AIO is more
> common than sync IO.  But I expect that when we sum across all the
> machines+workloads in the world, sync IO is more common and is hence the
> case we should optimise for.
> 
> That's assuming that the unlikely() actually does something.

But as Jeff said, that's not what unlikely is for.  It should only be 
used when it is unlikely for everybody, all the time, because when it is 
right, it helps rather little, but when it is wrong, it hurts a lot.

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