From: Sami Farin <7atbggg02@sneakemail.com>
To: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: vfat unlink latency 54.6ms for 128MB files
Date: Mon, 10 Jan 2005 03:23:30 +0200 [thread overview]
Message-ID: <20050110012330.GA10846@m.safari.iki.fi> (raw)
Just wondering, when I remove a 128MB file on vfat partition
(usb-storage, memcard reader), it causes 54.6ms latency
in rtc_latencytest... latency seems to increase linearly
as the filesize grows. I calculated 1s would be reached with
2344MB file but I didn't bother trying that yet.
Are there any possible fixes for fat fs so
that it doesn't disable interrupts for that long a time?
When I use loop device (the file on reiserfs), I get 45.9ms latency,
so this is not usb's fault.
These with Linux-2.6.10-ac8 on UP, PPro+, no preempt.
http://safari.iki.fi/vfat-unlink/
--
next reply other threads:[~2005-01-10 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 1:23 Sami Farin [this message]
2005-01-10 18:38 ` vfat unlink latency 54.6ms for 128MB files OGAWA Hirofumi
2005-01-10 19:39 ` Sami Farin
2005-01-10 22:36 ` Robert Hardy
2005-01-10 23:41 ` OGAWA Hirofumi
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=20050110012330.GA10846@m.safari.iki.fi \
--to=7atbggg02@sneakemail.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;
as well as URLs for NNTP newsgroup(s).