From: Zach Brown <zab@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: linux-next: manual merge of the vfs tree with the aio-direct tree
Date: Wed, 18 Sep 2013 10:06:30 -0700 [thread overview]
Message-ID: <20130918170630.GA2103@lenny.msi.event> (raw)
In-Reply-To: <20130918020035.GK13318@ZenIV.linux.org.uk>
> As for aio-direct... Two questions:
> * had anybody tried to measure the effect on branch predictor from
> introducing that method vector? Commit d6afd4c4 ("iov_iter: hide iovec
> details behind ops function pointers")
FWIW, I never did. I only went that route to begin with because the few
alternatives I tried before that were even more ugly :(. It's been long
enough that I can't quite remember what I'd tried, though.
- z
next prev parent reply other threads:[~2013-09-18 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 0:56 linux-next: manual merge of the vfs tree with the aio-direct tree Stephen Rothwell
2013-09-18 2:00 ` Al Viro
2013-09-18 3:25 ` Dave Kleikamp
2013-09-18 17:06 ` Zach Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-05 3:02 Stephen Rothwell
2013-09-05 2:54 Stephen Rothwell
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=20130918170630.GA2103@lenny.msi.event \
--to=zab@redhat.com \
--cc=dave.kleikamp@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.