linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Yogesh Pahilwan <pahilwan.yogesh@spsoftindia.com>
Cc: 'Neil Brown' <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Linux MD RAID5/6 bitmap patches
Date: Wed, 22 Mar 2006 13:06:48 -0500	[thread overview]
Message-ID: <44219238.9080905@steeleye.com> (raw)
In-Reply-To: <WM452680B12BAC48a19943A909AEA5F1C6@spsoftindia.com>

Yogesh Pahilwan wrote:

> Thanks for your reply. As far as what I understood that when we apply the
> bitmap patch, for every write it will do 2 sync writes that is setting the
> dirty bit, writing intent log and one async write for clearing the dirty
> bit. Is it correct?

The bits are in the intent log, so the "setting dirty bit" and "writing 
intent log" are the same thing. Just one write.

> If that is the case are there any patches available which can do collection
> of sync write in a queue and write a collection in single write request.
> For Eg:
> For 10 writes , we will have 10 + 1 sync writes + 10 async write.

The bitmap code already does this by default. The bitmap writes are 
queued up so that all writes to a given page (within a short time 
period) are reduced to a single write. The performance is actually quite 
good. There's very little performance difference between having a bitmap 
versus not having one.

> I mean to say , 10 sync writes for setting the dirty bits + 1 sync write for
> write intent log for all queued request in one write operation + 10 async
> write for clearing the dirty bit.

The async writes for clearing the bitmap are also combined.

--
Paul

  reply	other threads:[~2006-03-22 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22  7:22 Linux MD RAID5/6 bitmap patches Yogesh Pahilwan
2006-03-22 10:06 ` Neil Brown
2006-03-22 10:48   ` Yogesh Pahilwan
2006-03-22 18:06     ` Paul Clements [this message]
2006-03-23  9:12       ` Yogesh Pahilwan
2006-03-23 15:07         ` Paul Clements
  -- strict thread matches above, loose matches on Subject: below --
2006-03-22  7:27 Yogesh Pahilwan

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=44219238.9080905@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=pahilwan.yogesh@spsoftindia.com \
    /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).