From: random832@fastmail.com (Random832)
Subject: [TUHS] Another odd comment in V6
Date: Tue, 14 Feb 2017 10:50:59 -0500 [thread overview]
Message-ID: <1487087459.1747940.880726560.386E6275@webmail.messagingengine.com> (raw)
In-Reply-To: <CAH1jEzYCWh7ZGMfhFKeObdkSJN09AO9PUq6S-3Npv_Jdvndvsg@mail.gmail.com>
On Tue, Feb 14, 2017, at 09:18, Nick Downing wrote:
> Having a hypothetical system with a very slow disk (or fast
> CPU) in which disk accesses are blocking, would break many programs.
> cheers, Nick
That's not very hypothetical, but it is probably the reason disk access
(and even access to regular files on networked filesystems) isn't
interruptible, and non-blocking I/O useless in such situations, on some
modern systems.
next prev parent reply other threads:[~2017-02-14 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 8:46 Paul Ruizendaal
2017-02-14 11:27 ` Nick Downing
2017-02-14 12:27 ` Paul Ruizendaal
2017-02-14 12:46 ` Nick Downing
2017-02-14 14:03 ` Lars Brinkhoff
2017-02-14 14:18 ` Nick Downing
2017-02-14 15:50 ` Random832 [this message]
2017-02-14 14:14 Noel Chiappa
2017-02-14 14:35 ` Paul Ruizendaal
2017-02-14 15:48 ` Random832
2017-02-14 16:06 ` Dan Cross
2017-02-14 15:40 Noel Chiappa
2017-02-14 16:17 Noel Chiappa
2017-02-21 19:23 Norman Wilson
2017-02-22 9:59 ` Tony Finch
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=1487087459.1747940.880726560.386E6275@webmail.messagingengine.com \
--to=random832@fastmail.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;
as well as URLs for NNTP newsgroup(s).