From: Manfred Spraul <masp0008@stud.uni-sb.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: V Ganesh <ganesh@vxindia.veritas.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Possible optimization in ext2_file_write()
Date: Sat, 20 Mar 1999 16:33:46 +0100 [thread overview]
Message-ID: <36F3BFDA.ED1B42B7@stud.uni-sb.de> (raw)
In-Reply-To: 199903191448.OAA01416@dax.scot.redhat.com
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Thu, 18 Mar 1999 23:46:57 +0530 (IST), V Ganesh
> <ganesh@vxindia.veritas.com> said:
>
> > it looks like whenever we write a partial block which
> > doesn't exist in the buffer cache, ext2_file_write() (and
> > possibly the write functions of other filesystems) directly
> > reads that block from the block device without checking if
> > it is present in the page cache.
>
> Correct...
I don't know what you are exactly talking about, but there is another
problem except speed:
Most modern harddisks remap bad sectors, so sometimes you can't read a
sector, but if you write the sector is remapped.
I.e. if you "create a new file, write 400 bytes, close the file, sync",
then the data sector should not be read.
Our current Windows 95 & Windows NT file system drivers read the data
sector, and that has caused problems (older ZIP disks, SyQuest,
my own damnaged harddisk?-I don't remember the details).
Regards,
Manfred
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-03-20 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199903181816.XAA12650@vxindia.vxindia.veritas.com>
1999-03-19 14:48 ` Possible optimization in ext2_file_write() Stephen C. Tweedie
1999-03-20 15:33 ` Manfred Spraul [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=36F3BFDA.ED1B42B7@stud.uni-sb.de \
--to=masp0008@stud.uni-sb.de \
--cc=ganesh@vxindia.veritas.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.