From: Hans Reiser <reiser@namesys.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: "W. Wilson Ho" <ho@routefree.com>,
"Gryaznova E." <grev@namesys.botik.ru>,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-dev] Re: [reiserfs-list] Re: elevator algorithm in disk controller bad?
Date: Fri, 11 Jan 2002 22:30:19 +0300 [thread overview]
Message-ID: <3C3F3D4B.6060605@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10201110157240.9366-100000@master.linux-ide.org>
Andre Hedrick wrote:
>You mean like this ??
>
>ide.2.4.0-ac10.all.01212001.patch:
>+static int do_flush_cache(ide_drive_t *drive);
>ide.2.4.0-ac10.all.01212001.patch:
>+ (do_flush_cache(drive)) ? "SUCCESSED" : "FAILED");
>ide.2.4.0-ac10.all.01212001.patch:
>+static int do_flush_cache (ide_drive_t *drive)
>ide.2.4.0-ac10.all.01212001.patch:
>+ (do_flush_cache(drive)) ? "SUCCESSED" : "FAILED");
>ide.2.4.0-ac10.all.01212001.patch:
>- * all current requests to be flushed from the queue.
>ide.2.4.0-ac10.all.01212001.patch:
>+ * all current requests to be flushed from the queue.
>
>Or something more up to date?
>
>ide.2.4.16.12102001.patch:+ flushcache: NULL,
>ide.2.4.16.12102001.patch:+static int do_idedisk_flushcache(ide_drive_t *drive);
>ide.2.4.16.12102001.patch:+ if (do_idedisk_flushcache(drive))
>ide.2.4.16.12102001.patch:+static int do_idedisk_flushcache (ide_drive_t *drive)
>ide.2.4.16.12102001.patch:+ if (do_idedisk_flushcache(drive))
>ide.2.4.16.12102001.patch:+ flushcache: do_idedisk_flushcache,
>ide.2.4.16.12102001.patch:+ flushcache: NULL,
>ide.2.4.16.12102001.patch:+ flushcache: NULL,
>
> On Fri, 11 Jan 2002, Hans Reiser wrote:
>
>>Andre, have you had a chance to put in the the cache flushing stuff into
>>your IDE code?
>>
>>Hans
>>
>
><snip>
>
>This code as only been available for a year or so ...
>
>Regards,
>
>Andre Hedrick
>Linux ATA Development
>
>
>
Your code has been kept out of the main kernel for a year or so? Sigh.
I guess 2.4 has been freezing (except for VFS and MM which I will say
nothing about) for that long....
Chris and Edward, can you look at it and create a complementary patch to
make use of it that we can ask Andre to add to his patch, and then link
to his patch on our website?
Hans
prev parent reply other threads:[~2002-01-11 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C3EAB55.9070704@namesys.com>
2002-01-11 10:08 ` [reiserfs-dev] Re: [reiserfs-list] Re: elevator algorithm in disk controller bad? Andre Hedrick
2002-01-11 16:56 ` Chris Mason
2002-01-11 19:30 ` Hans Reiser [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=3C3F3D4B.6060605@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=andre@linux-ide.org \
--cc=grev@namesys.botik.ru \
--cc=ho@routefree.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox