| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Questions about XFS |
| From: | harryxiyou <harryxiyou@xxxxxxxxx> |
| Date: | Sat, 26 Oct 2013 00:24:07 +0800 |
| Cc: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=dGxOyLF1jWPRkUXqvYKCW9+aC7llF3abS5fYLwn3UN8=; b=00rVwrfkyoy2jKcEG6yU3AKTmb8rIRiy3OtTQZCFg+0RNh0qBhegylRPXbEMgV5rNx /CxM6p/Cpyhs6wKwPEVzok6COsBeCaGNswHH2/xK2eXU14Fw0pAacqgvsByIIDz294D1 oFqn/XhRgmQ+coH2v+0rC6feWB6f/d49t66KMAveUEGDBDw7aXfZtPVF51ibfn8ss4cV 6HXPl7fvefCH/Zmn/eMdhHm5SAawUz8CwzeqpVx5W3oxhyk8b7kdUAdarNz1QHfY1Uqs PM5EtNN02NdgbOuOlxUzUbUhkSUoXSou0rWBKt1K5BtIGrfMSOBZCG9JS3oYtU4VXeNI mnxA== |
| In-reply-to: | <526A86F2.9070400@xxxxxxxxxxx> |
| References: | <CAD+1EGPG1G9Q8kwaSUjxVjvx73UByLb3G0rmUbgJr+zD-CnjEw@xxxxxxxxxxxxxx> <20131025164255.46d2829c@xxxxxxxxxxxxxxxxxxxx> <526A86F2.9070400@xxxxxxxxxxx> |
On Fri, Oct 25, 2013 at 10:57 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> well, yes and no. It supports the "realtime subvolume" which is
> not really technically "realtime." It does have a more deterministic
> allocator, but it doesn't have GRIO (Guaranteed Realtime I/O) like
> IRIX does.
Hmmm..., however, I find the manual of mkfs.xfs tell me as follows.
-r realtime_section_options
These options specify the location, size, and other
parameters of the
real-time section of the filesystem. The valid
realtime_section_options
are:
rtdev=device
This is used to specify the device which
should contain the
real-time section of the filesystem. The
suboption value is
the name of a block device.
extsize=value
This is used to specify the size of the
blocks in the real-
time section of the filesystem. This value
must be a multiple
of the filesystem block size. The minimum
allowed size is the
filesystem block size or 4 KiB
(whichever is larger); the
default size is the stripe width for striped
volumes or 64
KiB for non-striped volumes; the maximum
allowed size is 1
GiB. The real-time extent size should be
carefully chosen to
match the parameters of the physical media used.
size=value
This is used to specify the size of the
real-time section.
This suboption is only needed if the
real-time section of the
filesystem should occupy less space than the
size of the par?
tition or logical volume containing the section.
After I run "mkfs.xfs -r rtdev=/dev/sda3 extsize=64K", I wonder what the
differences between '/dev/sda3' and '/dev/sda2' (/dev/sda2 is common XFS or
EXT2). The differences are as follows, right?
1, I/O speed of real-time '/dev/sda3' is faster?
2, The performance of '/dev/sda3â is better?
Anything else?
--
Thanks
Weiwei Jia (Harry Wei)
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Questions about XFS, Eric Sandeen |
|---|---|
| Next by Date: | Re: Questions about XFS, harryxiyou |
| Previous by Thread: | Re: Questions about XFS, Eric Sandeen |
| Next by Thread: | Re: Questions about XFS, harryxiyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |