From: Ankur Bose <ankur.bose@oracle.com>
To: linux-raid@vger.kernel.org
Subject: Write intent bitmap algorithm
Date: Fri, 20 May 2016 00:03:03 -0700 (PDT) [thread overview]
Message-ID: <cd14f4dd-a88a-4089-9b07-f16a221e003c@default> (raw)
Hi All,
We are doing performance analysis of MD raid1 and wanted to know the flow/algorithm of the writes with write intent bitmap.
As per "man md" below lines gives the algo
"Before any write request is honored, md will make sure that the corresponding bit in the log is set. After a period of time with no writes to an area of the array, the corresponding bit will be cleared."
Here we wanted to know after what period of time and what is the logic to calculate this period of time which MD does ?
I see a function "void bitmap_daemon_work(struct mddev *mddev)" in bitmap.c file but trying to figure out the logic how it is used.
Thanks,
ankur.
next reply other threads:[~2016-05-20 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 7:03 Ankur Bose [this message]
2016-05-22 23:19 ` Write intent bitmap algorithm NeilBrown
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=cd14f4dd-a88a-4089-9b07-f16a221e003c@default \
--to=ankur.bose@oracle.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 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).