From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Aligning file system data
Date: Tue, 29 Mar 2005 22:50:10 -0600 [thread overview]
Message-ID: <424A3002.0@shaw.ca> (raw)
In-Reply-To: <3ND9P-2LV-1@gated-at.bofh.it>
John Richard Moser wrote:
> How likely is it that I can actually align stuff to 31.5KiB on the
> physical disk, i.e. have each block be a track?
I don't think this is very likely. Even being able to find out what the
physical disk arrangement is, or whether it is consistent in terms of
track size, etc. seems unlikely.
>
> Rather than leveraging the track cache, would it be less expensive for
> me to simply read in blocks totaling about 16 or 32KiB all at once?
For block sizes that small I think that the kernel should be smart
enough to do this itself, there is no need to concern with such low
level details in the application.
> How much more latency is involved in (B) than in (C)? Does crossing a
> track boundary incur anything expensive?
Given that both the disk and the kernel will likely read far more than
32KB ahead I can't see much difference other than the overhead inside
your application..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-03-30 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ND9P-2LV-1@gated-at.bofh.it>
2005-03-30 4:50 ` Robert Hancock [this message]
2005-03-30 5:30 ` Aligning file system data John Richard Moser
2005-03-30 4:32 John Richard Moser
2005-03-30 5:37 ` Bernd Eckenfels
2005-03-30 5:40 ` Barry K. Nathan
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=424A3002.0@shaw.ca \
--to=hancockr@shaw.ca \
--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 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.