From: Christoph Hellwig <hch@infradead.org>
To: Robert S Peterson <rpeterso@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Andrew Morton <akpm@osdl.org>,
fs-devel mailing list <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] loop.c to use write ops for fs requiring special locking
Date: Thu, 30 Mar 2006 15:15:04 +0100 [thread overview]
Message-ID: <20060330141504.GA11516@infradead.org> (raw)
In-Reply-To: <1143677411.26193.43.camel@technetium.msp.redhat.com>
You still don't get it.
Calling address space operations directly from generic code is a layering
violation. This got added during late 2.3/2.4 series to get loop working
again at all. It's a pretty bad design in general. We fixed the read side
by adding ->sendfile, and something similar is still needed on the write
side. We got along with the broken write side because it kinda worked.
It doesn't work for your out of tree filesystem which isn't a problem per
se. If you want it fixed the only way to get there is to fix it for real
instead of adding another unmaintainable cludge. So either go ahead and
add a new file operation that is the counterpart to ->sendfile or go away.
And please take a look at Jens Axboe's splice patch, I suspect you could
easily piggyback on that.
next prev parent reply other threads:[~2006-03-30 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 21:52 [PATCH] loop.c to use write ops for fs requiring special locking Robert S Peterson
2006-03-28 0:44 ` Andrew Morton
2006-03-28 15:33 ` Robert S Peterson
2006-03-28 19:27 ` Andrew Morton
2006-03-28 14:40 ` Christoph Hellwig
2006-03-28 15:59 ` Robert S Peterson
2006-03-29 9:05 ` Christoph Hellwig
2006-03-30 0:10 ` Robert S Peterson
2006-03-30 14:15 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 16:48 [patch] " Robert S Peterson
2006-03-01 22:09 ` Andrew Morton
2006-03-02 10:16 ` Anton Altaparmakov
2006-03-10 23:04 ` Robert S Peterson
2006-03-10 23:13 ` Andrew Morton
2006-03-11 0:36 ` 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=20060330141504.GA11516@infradead.org \
--to=hch@infradead.org \
--cc=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rpeterso@redhat.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).