Two questions about stripe_cache_size
Two questions about stripe_cache_size
am 22.02.2011 22:46:57 von lopresti
(Thanks to Piergiorgio Sartor for pointing out this setting to me.)
I am looking for documentation on /sys/block/mdX/md/stripe_cache_size.
Specifically:
1) What are the units of this attribute?
2) I see it is supported for RAID 5. Is it supported for RAID 6?
Thanks!
- Pat
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:01:05 von NeilBrown
On Tue, 22 Feb 2011 13:46:57 -0800 "Patrick J. LoPresti"
wrote:
> (Thanks to Piergiorgio Sartor for pointing out this setting to me.)
>
> I am looking for documentation on /sys/block/mdX/md/stripe_cache_size.
> Specifically:
>
> 1) What are the units of this attribute?
Pages per device (1 page is 4K normally)
>
> 2) I see it is supported for RAID 5. Is it supported for RAID 6?
Yes.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:10:13 von Roberto Spadim
could add ' pages' or ' kB' after number? just to know what=B4s unit
2011/2/22 NeilBrown :
> On Tue, 22 Feb 2011 13:46:57 -0800 "Patrick J. LoPresti"
ail.com>
> wrote:
>
>> (Thanks to Piergiorgio Sartor for pointing out this setting to me.)
>>
>> I am looking for documentation on /sys/block/mdX/md/stripe_cache_siz=
e.
>> =A0Specifically:
>>
>> 1) What are the units of this attribute?
>
> Pages per device (1 page is 4K normally)
>
>>
>> 2) I see it is supported for RAID 5. =A0Is it supported for RAID 6?
>
> Yes.
>
> NeilBrown
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"=
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>
--=20
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:13:14 von lopresti
Thanks, Neil. Actually, I think I have one more question... (Well,
one question with many faces.)
Is the stripe cache write-back, or write-through? If the latter, when
does it get flushed to disk, exactly?
- Pat
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:24:22 von NeilBrown
On Tue, 22 Feb 2011 14:13:14 -0800 "Patrick J. LoPresti"
wrote:
> Thanks, Neil. Actually, I think I have one more question... (Well,
> one question with many faces.)
>
> Is the stripe cache write-back, or write-through? If the latter, when
> does it get flushed to disk, exactly?
>
Write-through.
However I am tempted to make it write-back as filesystems now submit 'flush'
requests which can be used to flush the cache. I wonder if you would be able
to notice any performance difference...
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:26:48 von Roberto Spadim
could we select it with sysfs?
2011/2/22 NeilBrown :
> On Tue, 22 Feb 2011 14:13:14 -0800 "Patrick J. LoPresti"
ail.com>
> wrote:
>
>> Thanks, Neil. =A0Actually, I think I have one more question... =A0(W=
ell,
>> one question with many faces.)
>>
>> Is the stripe cache write-back, or write-through? =A0If the latter, =
when
>> does it get flushed to disk, exactly?
>>
>
> Write-through.
>
> However I am tempted to make it write-back as filesystems now submit =
'flush'
> requests which can be used to flush the cache. =A0I wonder if you wou=
ld be able
> to notice any performance difference...
>
> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"=
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>
--=20
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Two questions about stripe_cache_size
am 22.02.2011 23:35:46 von lopresti
On Tue, Feb 22, 2011 at 2:24 PM, NeilBrown wrote:
>
>
> Write-through.
>
> However I am tempted to make it write-back as filesystems now submit =
'flush'
> requests which can be used to flush the cache. =A0I wonder if you wou=
ld be able
> to notice any performance difference...
I imagine it would depend on your file system and what you are doing wi=
th it.
In my application, I am typically generating multi-gigabyte files,
with linear writes, at a reasonably fast pace. So write-back might
help.
On the other hand, "flush" alone might not be sufficient for high
performance. I do not know much about Linux file system internals,
but it seems to me that there are two separate but related concepts.
One is ordering of operations (to ensure file system consistency).
The other is flushing (for data integrity; i.e. fsync()). If the file
system actually has to flush to ensure consistency -- rather than just
tagging its writes with ordering constraints -- I think you might lose
a lot of your performance to all of that flushing.
But since I really do not know what the kernel provides internally in
this regard I will stop rambling now.
- Pat
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html