linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: Zach Brown <zab@zabbo.net>,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Use case for "loop: Issue O_DIRECT aio with pages"?
Date: Fri, 2 Mar 2012 02:29:29 -0500	[thread overview]
Message-ID: <20120302072928.GA23725@infradead.org> (raw)
In-Reply-To: <20120301231524.GG32588@thunk.org>

I don't care about loop in particular, but this is important for any
in-kernel block device emulation using files, including the SCSI target
and a possible vhost-{block,scsi} implementation.

It's also the right way to implement swapping, instead of the braindead
swap over nfs proposals floating around currently.

  parent reply	other threads:[~2012-03-02  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 23:15 Use case for "loop: Issue O_DIRECT aio with pages"? Ted Ts'o
2012-03-02  2:49 ` Zach Brown
2012-03-02  8:14   ` Ted Ts'o
2012-03-02 14:52     ` Zach Brown
2012-03-02  7:29 ` Christoph Hellwig [this message]
2012-03-02 14:14 ` Chris Mason
2012-03-02 20:50   ` James Bottomley

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=20120302072928.GA23725@infradead.org \
    --to=hch@infradead.org \
    --cc=dave.kleikamp@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=zab@zabbo.net \
    /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).