mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grogan <grogan@pcnineoneone.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANN: New NTFS driver (2.0.0/TNG) now finished.
Date: Mon, 25 Mar 2002 12:17:25 -0500	[thread overview]
Message-ID: <20020325121725.71f6df02.grogan@pcnineoneone.com> (raw)
In-Reply-To: <5.1.0.14.2.20020325013452.03e53630@pop.cus.cam.ac.uk>

On Mon, 25 Mar 2002 02:26:41 +0000
Anton Altaparmakov <aia21@cam.ac.uk> wrote:

> Please everyone courageous enough to use a bleeding edge kernel and who is 
> also an NTFS user give this a try and let me know if you encounter any 
> problems! - Thanks!

Hello everyone

   I have been lurking here for a while on and off (to read the interesting discussions and learn). Since I've got a Windows XP installation on an NTFS partition on one of my hard disks, I went and got the 2.5.7 source and applied this patch last night.

It compiled cleanly with gcc 2.95.3 and is considerably faster than any of the old NTFS drivers. Before, there was a bit of a CPU intensive delay browsing directories in a file manager, like system32 and i386 with alot of files when they have to be initially read from disk. The perceived difference between the driver in 2.4.19-pre4 is certainly noticable on an older system like this one. (PII @266 with 128 Mb RAM). I figured I'd best measure something here, so I tried a bit of a test.

Now, I realize this test is flawed because it also tests file creation and buffers and cache and everything between the two kernels but it sure shows that someone is on the right track, somewhere.

On a fresh boot with 2.4.19-pre4:

bash-2.05$ time cp -r /mnt/windows3/windows/system32 /home/grogan/test

real    8m45.256s
user    0m0.730s
sys     6m27.030s

On a fresh boot with 2.5.7 with the new NTFS driver:

bash-2.05$ time cp -r /mnt/windows3/windows/system32 /home/grogan/test

real    3m13.190s
user    0m0.610s
sys     0m51.660s

This "test" was repeated twice under the same conditions, with negligible difference in the result (couple of seconds). Both of these disks are on the same IDE controller (/home is /dev/hda8 and the NTFS partition is /dev/hdb2). I must say I wasn't expecting such a drastic difference. The data appears to be intact. (correct size and number of files, anyway)

I wanted to send  a "thumbs up". Thanks, Anton, and everyone else that does what they do around here : - )

Grogan

On Mon, 25 Mar 2002 02:26:41 +0000
Anton Altaparmakov <aia21@cam.ac.uk> wrote:

> Please everyone courageous enough to use a bleeding edge kernel and who is 
> also an NTFS user give this a try and let me know if you encounter any 
> problems! - Thanks!
> 
> Best regards,
> 
> Anton
> 
> 
>

  parent reply	other threads:[~2002-03-25 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  2:26 Anton Altaparmakov
2002-03-25  8:32 ` David Woodhouse
2002-03-25 11:50   ` Brad Boyer
2002-03-25 12:32     ` Alan Cox
2002-03-25 12:52   ` Jeff Garzik
2002-03-25  8:38 ` Christoph Hellwig
2002-03-25 17:17 ` Grogan [this message]
2002-03-25 19:13   ` Anton Altaparmakov
2002-03-25 19:47   ` Bill Davidsen

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=20020325121725.71f6df02.grogan@pcnineoneone.com \
    --to=grogan@pcnineoneone.com \
    --cc=aia21@cam.ac.uk \
    --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

all inboxes | Powered by JetHome®