Originally posted by torsionbar28
View Post
Announcement
Collapse
No announcement yet.
Faster Reading From /dev/zero With Linux 5.10
Collapse
X
-
Originally posted by Christophe Leroy on lkmlWas measured on an 8xx powerpc running at 132MHz with:
dd if=/dev/zero of=/dev/null count=1M
With the patch, dd displays a throughput of 113.5MB/s
Without the patch it is 99.9MB/s
- Likes 1
Comment
-
Originally posted by OneTimeShot View PostWe need a /dev/uzero that doesn't block when the zeros are exhausted.
Joking aside, /dev/zero is important in all sorts of ways. Even if it is to just be able to mmap 1TB to write to disk.
Comment
-
Originally posted by gregzeng View Post
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.
So no, it's not for you, but nice to know that tiny details are improved.
- Likes 1
Comment
-
Originally posted by birdie View Post100% of a single core (Ryzen 7 3700X) which means it's CPU limited.Last edited by torsionbar28; 07 September 2020, 08:34 PM.
Comment
-
Originally posted by gregzeng View Postthe 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.
Which Linux distribution are you using? What kind of machine are you running it on? Have you posted about the problem in support forums for the distribution?
Comment
-
Originally posted by gregzeng View Post
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.
You likely have something in your fstab that isn't present during boot, and are using systemd as your init.
adding the option 'x-systemd.device-timeout=<number of seconds to wait>' to your drive's fstab entry should fix that, or switch your init system (I did the latter for a number of different reasons). Don't set the number to zero or it'll wait forever.
If you have an 'ntfs-3g' partition in your fstab, consider adding 'nobootwait' as well. nobootwait is only valid on certain filesystems, though. On Ubuntu, apparently, more kinds support it than in other distributions.
I don't have systemd init on any of my systems at the moment, but this was true when I did.Last edited by wyatt8740; 15 September 2020, 01:19 PM.
Comment
Comment