From: Warner Losh <imp@bsdimp.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Origin of the name 'strategy'
Date: Mon, 7 Jan 2019 14:21:00 -0700 [thread overview]
Message-ID: <CANCZdfrXQgsqsQYmYNw5L5dVE96Zs5PnJArZFcv0bsLzB0-EWw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
So what's the origin of the name 'strategy' for the I/O routine in Unix
that drivers provide? Everything I've found in the early papers just says
that's what the routine is called. Is there a story behind why it was
chosen? My own theory is that it's in the sense of 'coping strategy' when
the driver needs to service more I/O for the upper layers, but that's just
a WAG.
Warner
[-- Attachment #2: Type: text/html, Size: 479 bytes --]
next reply other threads:[~2019-01-07 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 21:21 Warner Losh [this message]
2019-01-07 21:27 ` Dave Horsfall
2019-01-07 21:28 ` Dan Cross
2019-01-07 22:28 ` Erik E. Fair
2019-01-09 20:51 ` Clem Cole
2019-01-09 23:30 ` Dave Horsfall
2019-01-09 5:42 Dave Horsfall
2019-01-09 12:02 ` Dan Cross
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=CANCZdfrXQgsqsQYmYNw5L5dVE96Zs5PnJArZFcv0bsLzB0-EWw@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=tuhs@tuhs.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).