From: Hans Reiser <reiser@namesys.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] batch-write.patch
Date: Wed, 05 Jul 2006 21:45:53 -0700 [thread overview]
Message-ID: <44AC9581.4090701@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606291609020.5747@turbotaz.ourhouse>
Chase, we incorporated your suggestion, and I want to thank you for it.
Hans
Chase Venters wrote:
> On Thu, 29 Jun 2006, Hans Reiser wrote:
>
>>
>> (patch was attached)
>>
>
> Not quoted because patch isn't inlined, but you're testing for the
> presence of the batch_write pointer repeatedly in the loop. How about
> declare a batch_write ptr on the stack and then do your test once,
> outside of your do { } while (count) loop, and then set it to the
> generic method (before entering the loop) if the generic method isn't
> available?
>
> Thanks,
> Chase
>
>
next prev parent reply other threads:[~2006-07-06 4:46 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 [this message]
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
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=44AC9581.4090701@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
/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.