From: Anthony Liguori <aliguori@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Khoa Huynh <khoa@us.ibm.com>,
pbadari@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] raw-posix: Linearize direct I/O on Linux NFS
Date: Fri, 15 Apr 2011 11:10:37 -0500 [thread overview]
Message-ID: <4DA86DFD.2020000@us.ibm.com> (raw)
In-Reply-To: <20110415153448.GA30116@lst.de>
On 04/15/2011 10:34 AM, Christoph Hellwig wrote:
> On Fri, Apr 15, 2011 at 04:26:41PM +0100, Stefan Hajnoczi wrote:
>> On Fri, Apr 15, 2011 at 4:05 PM, Christoph Hellwig<hch@lst.de> wrote:
>>> NAK. ?Just wait for the bloody NFS client fix to get in instead of
>>> adding crap like that.
>> That's totally fine if NFS client will be fixed in the near future but
>> this doesn't seem likely:
>>
>> http://www.spinics.net/lists/linux-nfs/msg20462.html
> The code to use preadv/pwritev has been in qemu for over 2 years,
> and it took people to notice the NFS slowdown until now, so don't
> expect it to be fixed three days layer.
>
> I can't event see you in the relevent threads arguing for getting it
> fixed, so don't complain.
In general, since we are userspace, we should try to run well on
whatever kernel we're on.
What I don't like about this patch is that likelihood of false
positives. We check for Linux and for NFS but that means an old
userspace is doing unoptimal things on newer kernels. Even if we had a
kernel version check, if the fix gets backported to an older kernel,
we'll still get a false positive.
Ideally, we'd be able to query the kernel to see whether we should
bounce or not. But AFAIK there is nothing even close to an interface to
do this today.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-04-15 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 13:40 [Qemu-devel] [PATCH] raw-posix: Linearize direct I/O on Linux NFS Stefan Hajnoczi
2011-04-15 15:05 ` Christoph Hellwig
2011-04-15 15:26 ` Stefan Hajnoczi
2011-04-15 15:34 ` Christoph Hellwig
2011-04-15 16:10 ` Anthony Liguori [this message]
2011-04-15 16:17 ` Stefan Hajnoczi
2011-04-15 17:27 ` Christoph Hellwig
2011-04-15 16:23 ` Badari Pulavarty
2011-04-15 17:29 ` Christoph Hellwig
2011-04-15 22:21 ` Badari Pulavarty
2011-04-15 23:00 ` Anthony Liguori
2011-04-15 23:33 ` Badari Pulavarty
2011-04-16 2:05 ` Christoph Hellwig
2011-04-16 8:46 ` Stefan Hajnoczi
2011-04-16 2:03 ` Christoph Hellwig
2011-04-15 18:09 ` Anthony Liguori
2011-04-15 18:25 ` Badari Pulavarty
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=4DA86DFD.2020000@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=hch@lst.de \
--cc=khoa@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=pbadari@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).