From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: Block I/O Enchancements, 2.5.1-pre2
Date: Tue, 27 Nov 2001 18:55:09 -0700 [thread overview]
Message-ID: <20011127185509.A1060@vger.timpanogas.org> (raw)
In-Reply-To: <15364.3457.368582.994067@gargle.gargle.HOWL> <Pine.LNX.4.33.0111271701140.1629-100000@penguin.transmeta.com> <20011127183418.A812@vger.timpanogas.org> <3C0441B4.B8194BEE@mandrakesoft.com>
In-Reply-To: <3C0441B4.B8194BEE@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Nov 27, 2001 at 08:45:24PM -0500
On Tue, Nov 27, 2001 at 08:45:24PM -0500, Jeff Garzik wrote:
> "Jeff V. Merkey" wrote:
> > 1. The changes made to submit_bh indicate I can now send long
> > chains of variable block size requests to the I/O layer similiar
> > to the capability of Windows 2000 and NetWare I/O subsystems.
>
> I don't want to speak for either Jens or Linus, but from what Jens was
> telling me months ago, and from my reading of Jens' earlier patches,
> this seems to indeed be the case. I've been looking forward to sending
> non-block-sized I/Os to and from a new filesystem I'm working on.
>
>
> > 3. In theory, I should be able to support page cache capability
> > for NWFS and possibly NTFS in Linux the way these wierd non-Unix
> > OS's work.
>
> If you are hacking on NTFS please make sure to base changes on
> "ntfs-driver-tng" in the "linux-ntfs" sourceforge cvs. It is now, as of
> the past week, completely modern to 2.4 vfs standards, and should
> support all read-only features except attribute lists.
I have a version that supports everything, including the journal,
and does not "barf" on writes. Unfortunately it's written in
"merkey code style" which is ThoseF_ckingLongAssNamesForEveryDamnFunction()
I was trained to write at Novell. Merging it into the sourceforge
version will be nasty. I have a few other projects and code I
am tardy in sending to Brazil :-). I think just letting Anton
review some of it may be a better approach. NWFS is first
up and needs to get finished and in so if I get hit by
a truck or killed by a deranged Novell employee who has
been recently laid off, someone can take maintain it.
:-)
Jeff
>
> Regards,
>
> Jeff
>
>
> --
> Jeff Garzik | Only so many songs can be sung
> Building 1024 | with two lips, two lungs, and one tongue.
> MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-28 1:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:44 2.5.1-pre2 does not compile f5ibh
2001-11-27 20:50 ` Linus Torvalds
2001-11-27 22:09 ` Christoph Hellwig
2001-11-27 22:22 ` onboard ethernet/sound on Soyo SY-K7V? Dax Kelson
2001-11-27 22:47 ` François Cami
2001-11-27 22:57 ` Jeff Garzik
2001-11-27 22:29 ` 2.5.1-pre2 does not compile Robert Love
2001-11-28 0:29 ` Linus Torvalds
2001-11-28 12:55 ` Christoph Hellwig
2001-11-28 16:26 ` Andreas Dilger
2001-11-28 16:42 ` Christoph Hellwig
2001-11-28 16:39 ` Martin Dalecki
2001-11-28 17:27 ` Andreas Dilger
2001-11-28 0:40 ` Andre Hedrick
2001-11-27 22:02 ` Paul Mackerras
2001-11-28 1:04 ` Linus Torvalds
2001-11-28 1:34 ` Block I/O Enchancements, 2.5.1-pre2 Jeff V. Merkey
2001-11-28 1:45 ` Jeff Garzik
2001-11-28 1:55 ` Jeff V. Merkey [this message]
2001-11-28 2:32 ` Jeff Garzik
2001-11-28 3:38 ` Linus Torvalds
2001-11-30 2:19 ` Daniel Phillips
2001-11-30 12:21 ` Hans Reiser
[not found] ` <15367.32910.275973.287742@laputa.namesys.com>
2001-12-01 9:31 ` [reiserfs-dev] " Hans Reiser
2001-11-28 10:17 ` Martin Dalecki
2001-11-28 13:35 ` Jens Axboe
2001-11-28 17:29 ` Jeff Merkey
2001-11-28 6:58 ` 2.5.1-pre2 does not compile Jens Axboe
2001-11-28 12:20 ` bio write-up (was: Re: 2.5.1-pre2 does not compile) Jens Axboe
2001-11-29 1:07 ` 2.5.1-pre2 bio offset by one error in VIA IDE Anton Altaparmakov
2001-11-28 23:31 ` Anton Altaparmakov
2001-11-28 23:55 ` Andreas Dilger
2001-11-30 1:53 ` 2.5.1-pre2 does not compile Daniel Phillips
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=20011127185509.A1060@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=axboe@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®