All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>,
	Andrew Morton <akpm@osdl.org>,
	lkml <Linux-Kernel@vger.kernel.org>,
	reiserfs-dev@namesys.com
Subject: Re: [PATCH 1/2] batch-write.patch
Date: Tue, 04 Jul 2006 11:43:32 -0700	[thread overview]
Message-ID: <44AAB6D4.1040101@namesys.com> (raw)
In-Reply-To: <84144f020607040507u58489b8eqfe8f41ef0d76b369@mail.gmail.com>

Pekka Enberg wrote:

> On 7/4/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
>
>> @@ -784,6 +786,8 @@ otherwise noted.
>>
>>    writev: called by the writev(2) system call
>>
>> +  batch_write: optional, if implemented called by writev(2) and
>> write(2)
>> +
>
>
> It'd be nice if you added some explanation here why a filesystem
> developer would want to implement it.
>
>                                       Pekka
>
>
Vladimir, it sounds like he found another place you might insert this
comment:

+/*
+ * When calling the filesystem for writes, there is processing
+ * that must be done:
+ * 1) per word
+ * 2) per page
+ * 3) per call to the FS
+ * If the FS is called per page, then it turns out that 3) costs more
+ * than 1) and 2) for sophisticated filesystems.  To allow the FS to
+ * choose to pay the cost of 3) only once we call batch_write, if the
+ * FS supports it.
+ */


Thanks Pekka!

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

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=44AAB6D4.1040101@namesys.com \
    --to=reiser@namesys.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=akpm@osdl.org \
    --cc=penberg@cs.helsinki.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.