All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: greg@enjellic.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Complexity of toggling write-behind.
Date: Thu, 14 Oct 2010 06:26:10 +1100	[thread overview]
Message-ID: <20101014062610.5aed76c2@notabene> (raw)
In-Reply-To: <201010131848.o9DImoXe007448@wind.enjellic.com>

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


      reply	other threads:[~2010-10-13 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 18:48 Complexity of toggling write-behind greg
2010-10-13 19:26 ` Neil Brown [this message]

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=20101014062610.5aed76c2@notabene \
    --to=neilb@suse.de \
    --cc=greg@enjellic.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.