From: Christian Barthel <bch@online.de>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] TUHS Digest, Vol 38, Issue 10
Date: Wed, 09 Jan 2019 20:13:19 +0100 [thread overview]
Message-ID: <875zux8x0w.fsf@x230.onfire.org> (raw)
In-Reply-To: <CANCZdfqV_t603Ac309iBwruKACih2+nXHu5KYPUzizYvznO+1g@mail.gmail.com> (Warner Losh's message of "Tue, 8 Jan 2019 21:23:54 -0700")
Warner Losh <imp@bsdimp.com> writes:
> The name seems obvious because I've seen it for the last 30 years. But I've
> not seen it used elsewhere, nor have I seen it documented except in
> relationship to Unix. [....]
It is also used by Erich Gamma's famous book "Design Pattern": The
Strategy Pattern. Is it somehow related to Unix (due to the reason that
the Unix device interface is designed in an object oriented fashion)?
Apart from that, U. Vahalia describes the strategy entry point in the
book "UNIX Internals: The new Frontiers" (ISBN 978-0131019089) as:
| d_strategy() - Common point for read and write requests to a block
| device. So named since the driver may use some strategy to reorder
| pending requests to optimize performance. Operates asynchronously - if
| the device is busy, the routine merely queues the request and returns.
| When the I/O completes, the interrupt handler will dequeue the next
| request and start the next I/O.
--
Christian Barthel
next prev parent reply other threads:[~2019-01-09 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1546912802.21858.tuhs@minnie.tuhs.org>
2019-01-08 10:15 ` Steve Simon
2019-01-08 11:00 ` Andreas Kusalananda Kähäri
2019-01-08 14:58 ` Warner Losh
2019-01-09 2:10 ` Dave Horsfall
2019-01-09 4:23 ` Warner Losh
2019-01-09 19:13 ` Christian Barthel [this message]
2019-01-09 5:19 ` Bakul Shah
2019-01-09 5:45 ` Warner Losh
2019-01-09 15:09 ` Bakul Shah
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=875zux8x0w.fsf@x230.onfire.org \
--to=bch@online.de \
--cc=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).