public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Andreas Dilger <adilger@sun.com>, Karel Zak <kzak@redhat.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	util-linux-ng@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.17 (stable)
Date: Sun, 10 Jan 2010 23:27:10 -0800	[thread overview]
Message-ID: <4B4AD2CE.8040207@zytor.com> (raw)
In-Reply-To: <yq1ocl187ww.fsf@sermon.lab.mkp.net>

On 01/10/2010 10:36 PM, Martin K. Petersen wrote:
>>>>>> "Andreas" == Andreas Dilger <adilger@sun.com> writes:
> 
> Andreas> I agree whole heartedly.  We steer users very sharply away from
> Andreas> using partitions at all, because on h/w RAID devices the
> Andreas> 512-byte offset from fdisk completely kills RAID-5/6
> Andreas> performance.
> 
> I don't have a problem aligning to 1MB (taking alignment_offset into
> account) by default but there needs to be an easy override.  There are
> RAID arrays that internally compensate for the legacy 63 sector offset
> and we'll cause misalignment if we start at 1MB on those.
> 
> I'm heavily lobbying our storage partners to make sure they fill out the
> right SCSI bits if their LUNs are not naturally aligned.  But there are
> obviously going to be legacy devices out there that will need manual
> alignment compensation.
> 

Yes, but we shouldn't default to braindead mode.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-01-11  7:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  9:33 [ANNOUNCE] util-linux-ng v2.17 (stable) Karel Zak
2010-01-08 21:43 ` H. Peter Anvin
2010-01-08 22:40   ` Andreas Dilger
2010-01-08 23:33     ` H. Peter Anvin
2010-01-11  6:36     ` Martin K. Petersen
2010-01-11  7:27       ` H. Peter Anvin [this message]
2010-01-11 14:05   ` Pavel Machek
2010-01-11 16:52     ` H. Peter Anvin
2010-01-11 20:17       ` Pavel Machek
2010-01-11 23:26         ` H. Peter Anvin
2010-01-12 13:33           ` Artem Bityutskiy
2010-01-12 13:35             ` Artem Bityutskiy
2010-01-11 19:17     ` Artem Bityutskiy
2010-01-12  7:19     ` Jörn Engel
2010-01-12  8:19       ` H. Peter Anvin
2010-01-12  9:37         ` Jörn Engel
2010-01-12 16:20           ` H. Peter Anvin

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=4B4AD2CE.8040207@zytor.com \
    --to=hpa@zytor.com \
    --cc=adilger@sun.com \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=util-linux-ng@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