From: Roberto Spadim <roberto@spadim.com.br>
To: Andras Korn <korn@raidlist.elan.rulez.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: write-behind has no measurable effect?
Date: Tue, 15 Feb 2011 06:10:17 -0300 [thread overview]
Message-ID: <AANLkTinAV4jJc8ueZ1mjRPpDnA_eWhUDcL8uz-0Ufifk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikFSOePZJXknAt=Tx6+FpdJ4tiSNwpuwuPC3RY=@mail.gmail.com>
andras could you make some benchmarks to raid1 with round robin read balance?
at this site:
www.spadim.com.br/raid1/
it's kernel 2.6.37 based
2011/2/15 Roberto Spadim <roberto@spadim.com.br>
>
> andras could you make some benchmarks to raid1 with round robin read balance?
> at this site:
> www.spadim.com.br/raid1/
>
> it's kernel 2.6.37 based
>
> 2011/2/14 Andras Korn <korn@raidlist.elan.rulez.org>
>>
>> On Tue, Feb 15, 2011 at 01:19:33AM +0000, John Robinson wrote:
>>
>> > >Another approach to take would be to mark as dirty, on the fast devices, all
>> > >areas being written to, and in the background continuously synch them to the
>> > >slow devices, sequentially (marking as clean synched-and-as-yet-unwritten-to
>> > >areas); so that the array would be resyncing continually, but be very fast
>> > >for random writes. This would of course also require the bitmap to only be
>> > >synchronously updated on the fast devices.
>> > >
>> > >Otoh, this is really a different mechanism from the current write-behind,
>> > >aimed at a different use-case, so maybe it could be implemented
>> > >orthogonally. (Patches welcome, I'm sure; it's times like these I hate not
>> > >being a coder.)
>> >
>> > I wonder whether bcache might do roughly what you want? I haven't
>>
>> It only does very roughly what I want (the idea there is to _cache_ a much
>> larger spinning disk using a relatively small SSD, whereas I basically want
>> them both to be the same size, with the disk eventually mirroring the
>> contents of the SSD); also, development of bcache has stalled (it doesn't
>> even compile with recent kernels and the developer has stated that he's
>> taking a break).
>>
>> I also know of flashcache, which is similar to bcache and is more actively
>> developed, but is still lagging quite a few versions behind (the latest
>> kernel it works with is 2.6.32, I think; it certainly doesn't compile with
>> 2.6.38).
>>
>> So, while both of these may actually be good at what they do, neither of
>> them does what I have in mind and I also can't use either of them because I
>> need a newer kernel than what they support.
>>
>> But thanks anyway.
>>
>> --
>> Andras Korn <korn at elan.rulez.org>
>> I'm not nearly as think as you confused I am.
>> --
>> 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
>
>
>
> --
> Roberto Spadim
> Spadim Technology / SPAEmpresarial
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
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
next prev parent reply other threads:[~2011-02-15 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 21:38 write-behind has no measurable effect? Andras Korn
2011-02-14 22:50 ` NeilBrown
2011-02-14 22:57 ` Andras Korn
2011-02-14 23:41 ` NeilBrown
2011-02-15 1:00 ` Andras Korn
2011-02-15 1:19 ` John Robinson
2011-02-15 2:19 ` Andras Korn
[not found] ` <AANLkTikFSOePZJXknAt=Tx6+FpdJ4tiSNwpuwuPC3RY=@mail.gmail.com>
2011-02-15 9:10 ` Roberto Spadim [this message]
2011-02-15 12:40 ` Andras Korn
2011-02-15 13:26 ` Roberto Spadim
2011-02-15 17:46 ` Roberto Spadim
2011-02-16 12:00 ` Andras Korn
2011-02-16 15:00 ` Roberto Spadim
2011-02-14 22:56 ` Doug Dumitru
2011-02-14 23:03 ` Andras Korn
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=AANLkTinAV4jJc8ueZ1mjRPpDnA_eWhUDcL8uz-0Ufifk@mail.gmail.com \
--to=roberto@spadim.com.br \
--cc=korn@raidlist.elan.rulez.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).