From: "Brian J. Conway" <dogbert@clue4all.net>
To: chaffee@bmrc.cs.berkeley.edu
Cc: linux-kernel@vger.kernel.org
Subject: VFAT access times in 2.4.1 kernel
Date: Wed, 31 Jan 2001 01:29:34 -0500 [thread overview]
Message-ID: <3A77B0CE.74C0F8BF@clue4all.net> (raw)
Hello, I just switched to 2.4.1 from 2.2.18 and have the kernel set up
in generally the same manner in terms of functionality. I've found that
VFAT access is incredibly slow in directories with a large number of
files. I have a single directory with approximately 1500 items, all
3-5MB apiece, and if I do 'ls -alt dir/ |more' on that directory, it
takes a full 2 seconds do list the contents of the first page. If I do
so again immediately afterwards it displays immediately, but the same
effects occur if I wait any considerable amount of time (> 2 minutes).
I've experienced no such problems under 2.2.18, and I'm running a 20GB
Maxtor drive running at UDMA(33) without any known issues. Any ideas?
Brian J. Conway
dogbert@clue4all.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-31 6:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A77B0CE.74C0F8BF@clue4all.net \
--to=dogbert@clue4all.net \
--cc=chaffee@bmrc.cs.berkeley.edu \
--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