linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Complexity of toggling write-behind.
@ 2010-10-13 18:48 greg
  2010-10-13 19:26 ` Neil Brown
  0 siblings, 1 reply; 2+ messages in thread
From: greg @ 2010-10-13 18:48 UTC (permalink / raw)
  To: neilb; +Cc: linux-raid

Hi Neil/linux-raid, hope the week is going well for everyone.

We implement a lot of geographically mirrored storage using Linux
RAID1 on the 'front-side' to access Linux servers running SCST for
storage backends.  One of the issues we are addressing are methods to
reduce I/O latency from the initiator's perspective when various
housekeeping operations are being done on the Linux backends, ie. RAID
check operations/re-synchronizations.

Write-mostly support is very helpful for reducing any read latencies.
To fully complete the loop it would be useful to leverage asynchronous
write-behind to eliminate write latency effects.  We use write-intent
bitmaps on the initiators so we are already preparted for that.

It is straight forward to toggle writemostly via the
/sys/mdN/md/rN/state pseudofiles but a review of the MD driver code in
at least 2.6.32.16 would suggest that write-behind is not readily
togglable.  That may have changed in most recent kernels but I don't
remember seeing any changelogs with your 'git pull' requests which
would suggest that.

Is this a function of support being a can of worms or just lack of
cycles?  If it is the latter I would be willing to take some
directional suggestions and see if we could get a prototype
implementation up and running.

Thanks much for any insight you may have.

Best wishes for a productive remainder of the week.

As always,
Dr. G.W. Wettstein, Ph.D.   IDfusion.org
4206 N. 19th Ave.           Unified health identity architecture.
Fargo, ND  58102
PH: 701-281-1686
FAX: 701-281-3949           EMAIL: greg@idfusion.org
------------------------------------------------------------------------------
"We don't know the OS that God uses, but the Vatican uses Linux."
                                -- Sister Judith Zoebelein
                                   Vatican Webmaster

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Complexity of toggling write-behind.
  2010-10-13 18:48 Complexity of toggling write-behind greg
@ 2010-10-13 19:26 ` Neil Brown
  0 siblings, 0 replies; 2+ messages in thread
From: Neil Brown @ 2010-10-13 19:26 UTC (permalink / raw)
  To: greg; +Cc: linux-raid

On Wed, 13 Oct 2010 13:48:50 -0500
greg@enjellic.com wrote:

> Hi Neil/linux-raid, hope the week is going well for everyone.
> 
> We implement a lot of geographically mirrored storage using Linux
> RAID1 on the 'front-side' to access Linux servers running SCST for
> storage backends.  One of the issues we are addressing are methods to
> reduce I/O latency from the initiator's perspective when various
> housekeeping operations are being done on the Linux backends, ie. RAID
> check operations/re-synchronizations.
> 
> Write-mostly support is very helpful for reducing any read latencies.
> To fully complete the loop it would be useful to leverage asynchronous
> write-behind to eliminate write latency effects.  We use write-intent
> bitmaps on the initiators so we are already preparted for that.
> 
> It is straight forward to toggle writemostly via the
> /sys/mdN/md/rN/state pseudofiles but a review of the MD driver code in
> at least 2.6.32.16 would suggest that write-behind is not readily
> togglable.  That may have changed in most recent kernels but I don't
> remember seeing any changelogs with your 'git pull' requests which
> would suggest that.
> 
> Is this a function of support being a can of worms or just lack of
> cycles?  If it is the latter I would be willing to take some
> directional suggestions and see if we could get a prototype
> implementation up and running.


In 2.6.33 and later you can write to /sys/block/mdX/md/bitmap/backlog

When there is a bitmap and backlog is non-zero, writes to read-mostly devices
a 'behind' writes (up to the limit of 'backlog').

NeilBrown


> 
> Thanks much for any insight you may have.
> 
> Best wishes for a productive remainder of the week.
> 
> As always,
> Dr. G.W. Wettstein, Ph.D.   IDfusion.org
> 4206 N. 19th Ave.           Unified health identity architecture.
> Fargo, ND  58102
> PH: 701-281-1686
> FAX: 701-281-3949           EMAIL: greg@idfusion.org
> ------------------------------------------------------------------------------
> "We don't know the OS that God uses, but the Vatican uses Linux."
>                                 -- Sister Judith Zoebelein
>                                    Vatican Webmaster


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-10-13 19:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-13 18:48 Complexity of toggling write-behind greg
2010-10-13 19:26 ` Neil Brown

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).