Faster Reading From /dev/zero With Linux 5.10

[phoronix]

Phoronix: Faster Reading From /dev/zero With Linux 5.10

Queued up in char-misc-next ahead of the Linux 5.10 cycle is a speed-up for reading from /dev/zero.....

http://www.phoronix.com/scan.php?page=news_item&px=Faster-Read-dev-zero-Linux-5.10

[rene]

At last, /dev/zero is finally plumbed for reasonable speeds required for a snappy Linux desktop and AAA games in 2020! Long overdue! ;-)

[birdie]

At last, /dev/zero is finally plumbed for reasonable speeds required for a snappy Linux desktop and AAA games in 2020! Long overdue! ;-)

pv -petrab /dev/zero > /dev/null

gives me 19.0GiB/s - can't complain that is close to the maximum memory throughput for this PC.

[OneTimeShot]

We need a /dev/uzero that doesn't block when the zeros are exhausted.

[rene]

pv -petrab /dev/zero > /dev/null

gives me 19.0GiB/s - can't complain that is close to the maximum memory throughput for this PC.

Phoronix will find some obvious ways to improve this long overdue ;-)

[THIRSTY GNOMES]

Sense some sarcasm in this discussion so far... but how would this compare to rng-tools for just performance (assuming that entropy is still better with rng-tools...)? Would be nice to have one less package to install with Packer.

[brouhaha]

Just mmap() /dev/zero. That's even faster.

[gregzeng]

Sense some sarcasm in this discussion so far... but how would this compare to rng-tools for just performance (assuming that entropy is still better with rng-tools...)? Would be nice to have one less package to install with Packer.

So much superior geek speak here, that I cannot understand the OP, nor the comments. Is this DEV ZERO the cause of the standard Linux "feature" of waiting 90 seconds for the "disk" to be located? It happens so frequently that most of us hate Linux. There seems to be a bad CFG fault somewhere that no person dares mention. The only way I know to work around it is to re-install the Linux system, on top of itself, without formatting the partition. Crazy error-causing Linux for any person who dares trying multi-booting.

[torsionbar28]

So much superior geek speak here, that I cannot understand the OP, nor the comments. Is this DEV ZERO the cause of the standard Linux "feature" of waiting 90 seconds for the "disk" to be located? It happens so frequently that most of us hate Linux. There seems to be a bad CFG fault somewhere that no person dares mention. The only way I know to work around it is to re-install the Linux system, on top of itself, without formatting the partition. Crazy error-causing Linux for any person who dares trying multi-booting.

Sounds like you might be dividing by zero. Don't worry, happens to the best of us sometimes.

[torsionbar28]

pv -petrab /dev/zero > /dev/null
gives me 19.0GiB/s - can't complain that is close to the maximum memory throughput for this PC.

I'm getting 6.85GiB/s on DDR3-1600, and 6.14GiB/s on DDR3-1066. Sounds like you must have one of those newfangled DDR4 whizboxes.