I have had a process stuck in D+ state, and need to run it still a few
times. If I use timeout, will it prevent this process being stuck in D+
state until a reboot?
Hmmm without being a maintainer. I would say cp -r is most used on
single disk, so one thread is using the maximum disk iops taking y time
to copy. What would solve using multiple threads each taking their share
of the maximum disk iops, and because of the scheduling and other
overhead finish
ssage-
From: L A Walsh [mailto:coreut...@tlinx.org]
Sent: vrijdag 28 juni 2019 13:15
To: Marc Roos
Cc: aglo; coreutils
Subject: Re: question about parallelism in cp command
On 2019/06/06 09:25, Marc Roos wrote:
>
> Hmmm without being a maintainer. I would say cp -r is most used on
>
> nd at a maximum rate of 16589.7124 mb/s with blocksize 67108864 (the
entire file at once).
> Why, I ask you, is dd that much slower? What is it 'actually' doing
with all the processing power available?
I really do not get what this thread is about. I thought it was spam
with this subject. Fi