From: Jens Axboe <axboe@kernel.dk>
To: rrs@researchut.com, linux-block@vger.kernel.org
Subject: Re: wb-buf-throttle feedback
Date: Fri, 9 Sep 2016 14:19:50 -0600 [thread overview]
Message-ID: <09938f88-2a74-cb95-4498-5fc883eba115@kernel.dk> (raw)
In-Reply-To: <7cb20dd5-a5a3-25d3-987b-d36e54cae2f7@fb.com>
On 09/09/2016 02:02 PM, Jens Axboe wrote:
> On 09/09/2016 01:00 PM, Ritesh Raj Sarraf wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Hi Jens,
>>
>> [Please CC me in replies. I'm not subscribed to the list]
>>
>> Based on your announcement about the writeback patches, I have picked
>> up your
>> changes for testing.
>>
>> I tested it on a 4.7.3 stable kernel with patches applied from your
>> axboe/wb-
>> buf-throttle-v4.7 branch.
>>
>>
>> Instead of the infamous dd use case, I picked up the other generic one
>> i.e. to
>> build the linux kernel.
>>
>>
>> Machine config:
>>
>> Intel(R) Core(TM) i5-4210U CPU @ 1.70GHzRAM: 8 GiB
>> Disk: Rotational SATA HDD Hitachi - 7200 RPM
>>
>>
>> The machine has 4 logical CPUs.
>>
>>
>> Unfortunately, the issue is still easily reproducible. Building a
>> kernel with
>> defaults, which results in make -j4, ended up stalling the entire OS.
>
> What drive is hosting the system and kernel build? I think the current
> branch isn't aggressive enough on SATA style QD=32 devices with write
> back caching, so if that's what you are running, it'd be great if you
> could try a patch or two so we can improve this situation for you.
>
> The v4.7 branch is outdated. Let me spin a new one, that's probably the
> best way to start.
The 4.7 branch has now been updated, it's fully uptodate with the
current 4.8 based branch. Would be great if you could try that. If you
still see slowdowns, try and change RWB_DEF_DEPTH. It's currently at 16,
scale it down to 4 or something like that.
--
Jens Axboe
next prev parent reply other threads:[~2016-09-09 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 19:00 wb-buf-throttle feedback Ritesh Raj Sarraf
2016-09-09 20:02 ` Jens Axboe
2016-09-09 20:19 ` Jens Axboe [this message]
2016-09-11 9:55 ` Ritesh Raj Sarraf
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=09938f88-2a74-cb95-4498-5fc883eba115@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=rrs@researchut.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