From: Andrew Morton <akpm@linux-foundation.org>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Alex Volkov <avcp-lkmail@usa.net>,
"'Jeff Garzik'" <jeff@garzik.org>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: aio is unlikely
Date: Fri, 18 May 2007 15:12:59 -0700 [thread overview]
Message-ID: <20070518151259.319e09da.akpm@linux-foundation.org> (raw)
In-Reply-To: <464E2098.8020900@cfl.rr.com>
On Fri, 18 May 2007 17:54:32 -0400
Phillip Susi <psusi@cfl.rr.com> wrote:
> 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.
It does? Tell us more.
next prev parent reply other threads:[~2007-05-18 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705092101.l49L1CF1023363@hera.kernel.org>
2007-05-09 22:06 ` aio is unlikely Jeff Garzik
2007-05-09 22:18 ` Andrew Morton
2007-05-09 22:37 ` Jeff Garzik
2007-05-18 20:49 ` Alex Volkov
2007-05-18 21:06 ` Andrew Morton
2007-05-18 21:11 ` Jeff Garzik
2007-05-18 21:54 ` Phillip Susi
2007-05-18 22:12 ` Andrew Morton [this message]
2007-05-18 22:37 ` Jeff Garzik
2007-05-19 3:43 ` Nick Piggin
2007-05-19 3:50 ` Jeff Garzik
2007-05-18 21:30 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070518151259.319e09da.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avcp-lkmail@usa.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox