From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] signals and blocked in I/O
Date: Sat, 2 Dec 2017 03:01:32 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1712020248370.99186@aneurin.horsfall.org> (raw)
In-Reply-To: <20171201154448.GL3924@mcvoy.com>
On Fri, 1 Dec 2017, Larry McVoy wrote:
> Does anyone remember the reason that processes blocked in I/O don't
> catch signals? When did that become a thing, was that part of the
> original design or did that happen in BSD?
Something to do with pending DMA transfers?
> I'm asking because I'm banging on FreeBSD and I can wedge it hard, to
> the point that it won't recover, by just beating on tons of memory.
That happens on my MacBook a lot :-) It "only" has 4GB memory, the most
it will ever take. In the meantime, my FreeBSD server, pretty much
running only Sendmail and Apache (and BIND), gets along just fine with
just 512MB (yes, really; it does not run X or anything).
Sigh... Sometimes I miss my old 11/40 with 124kw of memory and a handful
of users, the biggest memory hog probably being NROFF (we didn't have VI,
but used EM)...
Hey, anyone remember Editor for Mortals? The author ought to be shot for
naming something just one keystroke away from "rm file"...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-12-01 16:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:44 Larry McVoy
2017-12-01 15:53 ` Dan Cross
2017-12-01 16:11 ` Clem Cole
2017-12-01 16:18 ` Larry McVoy
2017-12-01 16:33 ` Warner Losh
2017-12-01 17:26 ` Larry McVoy
2017-12-01 19:10 ` Chris Torek
2017-12-01 23:21 ` Dave Horsfall
2017-12-01 21:33 ` Bakul Shah
2017-12-01 22:38 ` Larry McVoy
2017-12-01 23:03 ` Ralph Corderoy
2017-12-01 23:09 ` Larry McVoy
2017-12-01 23:42 ` Bakul Shah
2017-12-02 0:48 ` Larry McVoy
2017-12-02 1:40 ` Bakul Shah
2017-12-03 13:50 ` Ralph Corderoy
2017-12-04 16:36 ` arnold
2017-12-04 16:58 ` Arthur Krewat
2017-12-04 17:19 ` Warner Losh
2017-12-05 2:12 ` Bakul Shah
2017-12-04 22:07 ` Dave Horsfall
2017-12-04 22:54 ` Ron Natalie
2017-12-04 22:56 ` Warner Losh
2017-12-05 0:49 ` Dave Horsfall
2017-12-05 0:58 ` Arthur Krewat
2017-12-05 2:15 ` Dave Horsfall
2017-12-05 2:54 ` Clem cole
2017-12-02 14:59 ` Theodore Ts'o
2017-12-01 16:01 ` Dave Horsfall [this message]
2017-12-01 16:24 ` Warner Losh
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=alpine.BSF.2.21.1712020248370.99186@aneurin.horsfall.org \
--to=dave@horsfall.org \
/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).