From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: david@lang.hm
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>, Matthew Wilcox <matthew@wil.cx>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com
Subject: Re: ATA support for 4k sector size
Date: Wed, 25 Feb 2009 19:20:00 -0500 [thread overview]
Message-ID: <yq1fxi2gibz.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0902251609490.26625@asgard.lang.hm> (david@lang.hm's message of "Wed\, 25 Feb 2009 16\:13\:42 -0800 \(PST\)")
>>>>> "david" == david <david@lang.hm> writes:
david> even if we can't get them to give us any info from the drive
david> directly, we still want to allow the sysadmin to configure the
david> use of the systems when they can find the info in other ways.
You can specify RAID parameters on the mkfs.xfs command line today.
mke[234]fs have similar knobs.
david> if you have the smallest and largest I/O you can submit without a
david> penalty and the alignment, isn't the optimal I/O size everything
david> between these two? (or at least everything between these two may
david> be close enough that defining an 'optimal' size may not be
david> worthwhile)
These parameters come straight out of SCSI. I described them wrong.
maximum is the biggest I/O the device can handle, full stop. Optimal is
the preferred I/O size for the array.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-02-26 0:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 22:24 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 1/2] ata: Define new commands from ATA8 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 2/2] ata: Add support for Long Logical Sectors and Long Physical Sectors Matthew Wilcox
2009-02-25 22:53 ` ATA support for 4k sector size H. Peter Anvin
2009-02-25 23:27 ` Martin K. Petersen
2009-02-25 23:33 ` H. Peter Anvin
2009-02-25 23:51 ` Martin K. Petersen
2009-02-26 12:43 ` Karel Zak
2009-02-26 15:17 ` H. Peter Anvin
2009-02-25 23:42 ` H. Peter Anvin
2009-02-25 23:55 ` Martin K. Petersen
2009-02-25 23:57 ` H. Peter Anvin
2009-02-26 0:07 ` Martin K. Petersen
2009-02-26 0:10 ` H. Peter Anvin
2009-02-26 0:17 ` Martin K. Petersen
2009-02-25 23:49 ` david
2009-02-26 0:04 ` Martin K. Petersen
2009-02-26 0:13 ` david
2009-02-26 0:20 ` Martin K. Petersen [this message]
2009-02-26 2:50 ` Theodore Tso
2009-02-26 3:05 ` Martin K. Petersen
2009-02-26 3:07 ` Matthew Wilcox
2009-02-26 3:23 ` Martin K. Petersen
2009-12-11 7:05 ` James Andrewartha
2009-12-11 7:26 ` H. Peter Anvin
2009-12-11 7:32 ` Martin K. Petersen
2009-02-26 5:16 ` Martin K. Petersen
2009-02-26 12:36 ` Matthew Wilcox
2009-02-26 15:32 ` H. Peter Anvin
2009-02-26 20:35 ` Martin K. Petersen
2009-02-26 21:02 ` H. Peter Anvin
2009-03-16 14:51 ` Greg Freemyer
2009-03-16 16:27 ` H. Peter Anvin
2009-03-16 17:37 ` Greg Freemyer
2009-03-16 18:11 ` H. Peter Anvin
2009-03-22 1:20 ` Bill Davidsen
2009-03-18 14:33 ` James Bottomley
2009-02-26 18:22 ` hdparm-9.12 released Mark Lord
2009-03-21 13:47 ATA support for 4k sector size Andries E. Brouwer
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=yq1fxi2gibz.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=david@lang.hm \
--cc=hpa@zytor.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sandeen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome