public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Christoph Hellwig <hch@infradead.org>, Andrew Morton <akpm@osdl.org>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
	lkml <Linux-Kernel@vger.kernel.org>,
	reiserfs-dev@namesys.com
Subject: Re: [PATCH 1/2] batch-write.patch
Date: Tue, 04 Jul 2006 10:44:13 -0700	[thread overview]
Message-ID: <44AAA8ED.5030906@namesys.com> (raw)
In-Reply-To: <20060704114836.GA1344@infradead.org>

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
>not the much higher file level.  Maybe all three should become callbacks
>for the generic write routines, but that's left for the future.
>
>
>  
>
I don't have a commitment to one way or the other, probably because
there are some things that are unclear in my mind.  Could you help me
with them?  Can you define what is the address space vs. the file level
please?  It is odd to be asking such a basic question, but these things
are genuinely unclear to me.  If the use of something varies according
to the file, is it a file method?  What things vary according to address
space and not according to file?  Should things that vary according to
address space be address space ops and things that vary according to
file be file ops?  If that logic seems valid, should a lot more be changed?

Oh, and Andrew, while such things are discussed, could you just pick one
way or the other and let the patch go in?

Hans

  reply	other threads:[~2006-07-04 17:44 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 [this message]
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

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=44AAA8ED.5030906@namesys.com \
    --to=reiser@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