From: Andrew Morton <akpm@osdl.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: nathans@sgi.com, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: RFC: [PATCH-2.6] Add helper function to lock multiple page cache pages.
Date: Sun, 6 Feb 2005 12:42:36 -0800 [thread overview]
Message-ID: <20050206124236.264f0cd4.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0502061932270.21938@hermes-1.csi.cam.ac.uk>
Anton Altaparmakov <aia21@cam.ac.uk> wrote:
>
> On Thu, 3 Feb 2005, Andrew Morton wrote:
> > I did a patch which switched loop to use the file_operations.read/write
> > about a year ago. Forget what happened to it. It always seemed the right
> > thing to do..
>
> How did you implement the write?
It was Urban, actually. Memory fails me.
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=102133217310200&w=2
It won't work properly for crypto transformations - iirc we decided it
would need to perform a copy.
next prev parent reply other threads:[~2005-02-06 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 15:12 Anton Altaparmakov
2005-02-02 15:43 ` Matthew Wilcox
2005-02-02 15:56 ` Anton Altaparmakov
2005-02-02 22:34 ` Andrew Morton
2005-02-03 10:37 ` Anton Altaparmakov
2005-02-03 10:47 ` Andrew Morton
2005-02-03 11:23 ` Anton Altaparmakov
2005-02-03 19:23 ` RFC: [PATCH-2.6] Add helper function to lock multiple page cache pages - nopage alternative Bryan Henderson
2005-02-04 15:36 ` Anton Altaparmakov
2005-02-04 17:17 ` Hugh Dickins
2005-02-03 19:03 ` RFC: [PATCH-2.6] Add helper function to lock multiple page cache pages - loop device Bryan Henderson
2005-02-06 19:42 ` RFC: [PATCH-2.6] Add helper function to lock multiple page cache pages Anton Altaparmakov
2005-02-06 20:42 ` Andrew Morton [this message]
2005-02-16 21:56 ` Anton Altaparmakov
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=20050206124236.264f0cd4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=viro@parcelfarce.linux.theplanet.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome