From: jim owens <owens6336@gmail.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: David Newall <davidn@davidnewall.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jeff Garzik <jeff@garzik.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Akira Fujita <a-fujita@rs.jp.nec.com>
Subject: Re: defrag deployment status (was Re: [PATCH] ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode)
Date: Mon, 08 Mar 2010 12:11:17 -0500 [thread overview]
Message-ID: <4B952FB5.2060600@gmail.com> (raw)
In-Reply-To: <87f94c371003080831n4d310e10i2b9badf4290f1ede@mail.gmail.com>
Greg Freemyer wrote:
>
> Jim, I should know this, but is sector 0 on the outside edge, or the inner edge?
>
> I assume outer so that the linear speed of the platter under the head
> is faster and thus more data per second is passing under the head.
Correct. AFAIK everyone starts 0 at the outer edge for that reason,
it makes for better benchmarks ;)
When I only worried about a few OEM drives, I used to read the zone
geometry from the drive to see where each speed transition was as the
density decreased. But that is just not worth the effort in linux
filesystems IMO, it is enough to pack low.
jim
next prev parent reply other threads:[~2010-03-08 17:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 20:32 [PATCH] ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode Christian Borntraeger
2010-03-07 23:27 ` defrag deployment status (was Re: [PATCH] ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode) Jeff Garzik
2010-03-08 5:43 ` Eric Sandeen
2010-03-08 7:53 ` Christian Borntraeger
2010-03-08 15:33 ` David Newall
2010-03-08 16:00 ` Christian Borntraeger
2010-03-08 16:22 ` jim owens
2010-03-08 16:31 ` Greg Freemyer
2010-03-08 17:11 ` jim owens [this message]
2010-03-09 13:23 ` jim owens
2010-03-08 19:38 ` Valdis.Kletnieks
2010-03-08 20:48 ` jim owens
2010-03-09 16:19 ` David Newall
2010-03-08 5:47 ` [PATCH] ext4: allow defrag (EXT4_IOC_MOVE_EXT) in 32bit compat mode Eric Sandeen
2010-03-08 8:42 ` Akira Fujita
2010-03-12 7:01 ` [PATCH resend] " Christian Borntraeger
2010-04-02 21:48 ` [PATCH] " tytso
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=4B952FB5.2060600@gmail.com \
--to=owens6336@gmail.com \
--cc=a-fujita@rs.jp.nec.com \
--cc=borntraeger@de.ibm.com \
--cc=davidn@davidnewall.com \
--cc=greg.freemyer@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ext4@vger.kernel.org \
--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).