From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 705d6bbb for ; Mon, 7 Jan 2019 21:29:34 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id B4D53A3711; Tue, 8 Jan 2019 07:29:33 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id DDA8E94EB9; Tue, 8 Jan 2019 07:29:20 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="kM0r1bJI"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 13DED94EB9; Tue, 8 Jan 2019 07:29:20 +1000 (AEST) Received: from mail-qk1-f169.google.com (mail-qk1-f169.google.com [209.85.222.169]) by minnie.tuhs.org (Postfix) with ESMTPS id 7719394C66 for ; Tue, 8 Jan 2019 07:29:19 +1000 (AEST) Received: by mail-qk1-f169.google.com with SMTP id 189so1157937qkj.8 for ; Mon, 07 Jan 2019 13:29:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TJWGsY9czGx2e4V/SggjAth03TU70+eQK4YXvS6wAZY=; b=kM0r1bJIoR/1KSwMU62NFKp6U4CTwmxdQSTK4nEG9xOE0bHstn994Ob1IqGOIv9vPC MuzqiDT2A39roobjU1LvGKNfvITF07DOduU/ne8dr2U6loUzwGGKffWgmrfJ/dheKZSK a0A2Ry2yB6p+whF7rML7gpmfFmmKF8dINUbYIb1WYd2J/bFZNf7LicxvMcj93xRKeuez WYm7PcUKmI4ISMARGkro3559WbOi8PQNrQ33pMAePeJsQUbMtcuFVFVKEoZjOS+8qT1l a7yi8m789zua54FvCEXTrAn2Z/YgjNVbuwijq1+fnAR7uofA6GB7cpECcuN7eFkesapW ks6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TJWGsY9czGx2e4V/SggjAth03TU70+eQK4YXvS6wAZY=; b=onS8YBcd3Kdq2UZemj/+kqnZ5LRfwRWkxx70nz99XQfZEBDGhbf1oMh2o9q6mLmKEQ SU2/6dbl7N/ya3hgmkNaAC2F59HWFbe7Wah4fmywCfohYOUFPAsjr9Qh+lcDN0D8iH44 v5hlvfPlmfSuE3pOIxW3va801yBjTf7fNMa7hpt0CqQqYLWrw7AJxXcNP0y+caiRgrrN oOjpU3RY4GqJMT1KE/wrVaBYKcz6yyDYXGUbXRqJI7GyDH8u1P89PwPyKk2NT7F3MOps z0RqUoDz+Ez8wnMuK1z3N6M+k0zCxyEByjLakLUbRJ3DkLs6D5I/QX+zXbqI6q3vZDWq ymnA== X-Gm-Message-State: AJcUukcXrAqM7bJ43sDlQ9+hzD0QLv/wnHguBxpW/xTEy9Nb9OK1dd8T vEdns/LzXPmUFi8qF157wxYfOak/OALASTPUzeA= X-Google-Smtp-Source: ALg8bN7W85TVclYLtuR914JmALAsJGVw77bnwPpKGCGF6pCfPHMS6ojYVWxNArqsSxNEynbp+8KG6x1bO9sxa91WJ3U= X-Received: by 2002:a37:6584:: with SMTP id z126mr56230160qkb.295.1546896558490; Mon, 07 Jan 2019 13:29:18 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dan Cross Date: Mon, 7 Jan 2019 16:28:42 -0500 Message-ID: To: Warner Losh Content-Type: multipart/alternative; boundary="000000000000df8ab6057ee4eb31" Subject: Re: [TUHS] Origin of the name 'strategy' X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000df8ab6057ee4eb31 Content-Type: text/plain; charset="UTF-8" On Mon, Jan 7, 2019 at 4:22 PM Warner Losh wrote: > 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. > I always thought it had to do with computing the optimal strategy for writing blocks to the disc device.... I wonder where I got that impression from. Perhaps reading Bach? - Dan C. --000000000000df8ab6057ee4eb31 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jan 7, 2019 at 4:22 PM Warner Losh <imp@bsdimp.com> wrote:
So what's the origin of t= he name 'strategy'=C2=A0 for the I/O routine in Unix that drivers p= rovide? 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 o= wn theory is that it's in the sense of 'coping strategy' when t= he driver needs to service more I/O for the upper layers, but that's ju= st a WAG.

I always thought it had to = do with computing the optimal strategy for writing blocks to the disc devic= e....=C2=A0 I wonder where I got that impression from.=C2=A0 Perhaps readin= g Bach?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dan C.
=
=C2=A0
--000000000000df8ab6057ee4eb31--