From: Xiao Ni <xni@redhat.com>
To: linux-raid@vger.kernel.org
Cc: jes sorensen <jes.sorensen@redhat.com>
Subject: Will the write request starve?
Date: Wed, 3 Sep 2014 01:59:08 -0400 (EDT) [thread overview]
Message-ID: <1482714710.31831797.1409723948805.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1275697636.31829381.1409722922411.JavaMail.zimbra@redhat.com>
Hi all
I meet a problem and I can't find the answer. Could you help me?
When raid5d want to handle a request, it need to get stripes by __get_priority_stripe.
In the __get_priority_stripe function, it always try to get stripe from handle_list.
Make an assumption that the raid of level 5 is assembled with 4 disks, and the raid
is normal. Now the a write request just want to write a single chunk, so we choose RMW
and the stripe will put on the delay_list, then activate it and put it to hold_list.
But if there are many read requests after the write request, when raid5d handle stripes
it will get stripe from handle_list. So will the write request starve?
Certainly I know it will not, because many tests have been done. But I can't find
the reason why it will not starve.
And there is a variable bypass_count, what's the function about it? If bypass_count <
bypass_threshold, it can get a chance to wait for the next write request to get a full write.
So avoid read requests. Am I right?
Best Regards
Xiao
next parent reply other threads:[~2014-09-03 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1275697636.31829381.1409722922411.JavaMail.zimbra@redhat.com>
2014-09-03 5:59 ` Xiao Ni [this message]
2014-09-03 8:18 ` Will the write request starve? Xiao Ni
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=1482714710.31831797.1409723948805.JavaMail.zimbra@redhat.com \
--to=xni@redhat.com \
--cc=jes.sorensen@redhat.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).