public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-dev@namesys.com
Cc: Christoph Hellwig <hch@infradead.org>,
	"Vladimir V. Saveliev" <vs@namesys.com>,
	Andrew Morton <akpm@osdl.org>,
	lkml <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] batch-write.patch
Date: Wed, 5 Jul 2006 09:06:58 +0400	[thread overview]
Message-ID: <200607050906.58879.zam@namesys.com> (raw)
In-Reply-To: <20060704114836.GA1344@infradead.org>

On Tuesday 04 July 2006 15:48, Christoph Hellwig wrote:
> On Tue, Jul 04, 2006 at 03:12:56PM +0400, Vladimir V. Saveliev wrote:
> > > Should this be an address_space_operation or a file_operation?
> >
> > I was seeking to be minimal in my changes to the philosophy of the
> > code. So, it was an address_space operation. Now it is a file
> > operation.
>
> It definitly should not be a file_operation! 
 
> It works at the 
> address_space 

generic_batch_write works with the page cache, another batch_write 
implementation may not.

Except the cached_page and pagevec which are generic_batch_write 
context, the batch_write switch leaves file stuff _before_ the switch 
and using of the page cache _after_ the switch.  It gives much 
flexibility to a file system to choose between simple page cache 
buffered write, batch version of page cache write or even not a 
page-oriented write method like reiser4 write method for packed (tails 
only) files.  address space op which does not use the page cache looks 
better as a file op.

> not the much higher file level.

> Maybe all three should 
> become callbacks for the generic write routines, but that's left for
> the future.

Thanks,
Alex.


      parent reply	other threads:[~2006-07-05  5:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 19:17 [PATCH 1/2] batch-write.patch Hans Reiser
2006-06-29 21:11 ` Chase Venters
2006-06-29 21:21   ` Chase Venters
2006-07-06  4:45   ` Hans Reiser
2006-06-30  1:50 ` Andrew Morton
2006-07-04 11:12   ` Vladimir V. Saveliev
2006-07-04 11:21     ` Vladimir V. Saveliev
2006-07-04 12:07       ` Pekka Enberg
2006-07-04 18:43         ` Hans Reiser
2006-07-04 11:48     ` Christoph Hellwig
2006-07-04 17:44       ` Hans Reiser
2006-07-04 22:18         ` Andrew Morton
2006-07-04 22:25           ` Hans Reiser
2006-07-04 22:39           ` Hans Reiser
2006-07-05 16:45           ` Vladimir V. Saveliev
2006-07-05 19:26             ` Andrew Morton
2006-07-06  4:58               ` Hans Reiser
2006-07-10 21:12                 ` Andreas Dilger
2006-07-09 20:11             ` Christoph Hellwig
2006-07-05  5:06       ` Alexander Zarochentsev [this message]

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=200607050906.58879.zam@namesys.com \
    --to=zam@namesys.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=reiserfs-dev@namesys.com \
    --cc=vs@namesys.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