All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] Handle group offsets in UFS1
Date: Thu, 13 Aug 2009 22:58:18 +0200	[thread overview]
Message-ID: <20090813205817.GP22130@thorin> (raw)
In-Reply-To: <d7ead6de0908131325i53cfd84diee33078dab167402@mail.gmail.com>

On Thu, Aug 13, 2009 at 10:25:15PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Thu, Aug 13, 2009 at 10:05 PM, Robert Millan<rmh@aybabtu.com> wrote:
> > On Thu, Aug 13, 2009 at 06:04:35PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >
> > This looks a bit odd (a mask applied to an integer?), but if it's really
> > this way, please go ahead with it.
> >
> It's the so-called skewness.
> Let's say you place inodes on addresses (C/H/S)
> (0/0/1) and (1/0/1) you first read the metadata at (0/0/1) then you
> try to fetch the metadata from (0/1/1). Responding to your request
> harddrive moves the head to cylinder number 1 but it takes some time.
> Meanwhile the plates have spinned (they are spinning constantly) and
> perhaps head is above sector (1/0/10) and you need to wait for
> complete rotation to fetch your sector.
> If you write inodes at (0/0/1) and (1/0/15) you will need to wait only
> for 4 sectors. This is called skewness and was an optimisation
> technique in the past. But now OS doesn't know about physical geometry
> and so can't do such kind of optimisation. I suppose it's why it's not
> used anymore for UFS2. I don't know if FreeBSD variant of UFS1 still
> uses this feature.

I see :-)

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-08-13 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 16:04 [PATCH 2/2] Handle group offsets in UFS1 Vladimir 'phcoder' Serbinenko
2009-08-13 20:05 ` Robert Millan
2009-08-13 20:14   ` Seth Goldberg
2009-08-13 20:25   ` Vladimir 'phcoder' Serbinenko
2009-08-13 20:58     ` Robert Millan [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=20090813205817.GP22130@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.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.