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.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
