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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 d4f436dc for ; Mon, 7 Jan 2019 21:21:51 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id C0070A371B; Tue, 8 Jan 2019 07:21:49 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id C1E1394C66; Tue, 8 Jan 2019 07:21:16 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=bsdimp-com.20150623.gappssmtp.com header.i=@bsdimp-com.20150623.gappssmtp.com header.b="x8hrXvd8"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 1E72B94EB9; Tue, 8 Jan 2019 07:21:14 +1000 (AEST) Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) by minnie.tuhs.org (Postfix) with ESMTPS id 74A1E94C66 for ; Tue, 8 Jan 2019 07:21:13 +1000 (AEST) Received: by mail-qt1-f173.google.com with SMTP id r14so2185355qtp.1 for ; Mon, 07 Jan 2019 13:21:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=SMmB3rAqF+dwhBgnmX5GnVgzDEVsWNfDiWkk3bF7Vug=; b=x8hrXvd8z2WvOkR9dawr+aSZZ2TrNo2i0AkjgnIjWbczgE7fh93p+QvO7am4oMKdX/ 02bUmFPkmTfodUiJstKuZHovxOiI8fk2cPrtQfJDph2K0BV/vR643WUnV2RP/XGMz+Iv 0L4IvXbp4IVO75mX6tZ0wYVUHwG3VYsCfkZw8dHzKcnsGswDkJcus1FlXJ88aamsIC7x 3i7PZZ4qZ2id5zyGLC9MFwVbXCp8QhtG251LuO74sANyZGbIjiuoFY10L3yLKL0TbSSy 05URRAX/z+Ak92ZsUVUpw6ZX4CH93yDQCu5TDRs2rrGG9jy5uK8+YoBFJzQY14pzSy5E m6+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=SMmB3rAqF+dwhBgnmX5GnVgzDEVsWNfDiWkk3bF7Vug=; b=XlCKT9MqLCFxGvM/lLb3e9a4d9VR+jk17P8pBke8t00y5q3RW4RmzKA0E5Qt4xU8hA lyi02Rwoxq7PgYWk7O/GCkjt13LVh42g/HpuqNz0SKdSl38fwHp9xS6wCetwFlYvJiZU e02PvU+D0p6GSZV7n0GsQ3cpmqRocHypccjx6vQxUR6Aj6ja8Le/4RpEM6RNmMVPgyp/ 6p+80gfGCOWqiwfvHKevkK+kYJa1UX0/N00e9xFP7+2NVvR0J15/l2jedBcZEfFaOLV7 a16ij0aW4e0KDxlZVQi9gwgnZHRSuk6zqWcZQVqRtKv2vx5wsvsHYMWyAdCxQNPNAKyp sdsw== X-Gm-Message-State: AJcUukegoN2NeJXVSTh3UjEheD1wjEa7lxQZOhE9/qBCgGJNFIGYm1sc XLRernUfGODTEJE+b1LMu5NsBN4ne6EkOCPyF5Mmynl7 X-Google-Smtp-Source: ALg8bN5W3z7qAEBlFsnMr8LtUtH9jtAkZm5SRIOacq7v2t8R3GB1JkVbY1ZxcKEF8bpG2ugPDuy8LfYfajpyEhbBf6Q= X-Received: by 2002:ac8:42c1:: with SMTP id g1mr29755381qtm.118.1546896072175; Mon, 07 Jan 2019 13:21:12 -0800 (PST) MIME-Version: 1.0 From: Warner Losh Date: Mon, 7 Jan 2019 14:21:00 -0700 Message-ID: To: The Eunuchs Hysterical Society Content-Type: multipart/alternative; boundary="000000000000e30d28057ee4cecf" Subject: [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: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000e30d28057ee4cecf Content-Type: text/plain; charset="UTF-8" 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 --000000000000e30d28057ee4cecf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
So what's the origin of the name 'strategy'=C2= =A0 for the I/O routine in Unix that drivers provide? Everything I've f= ound in the early papers just says that's what the routine is called. I= s 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 mo= re I/O for the upper layers, but that's just a WAG.

= Warner

--000000000000e30d28057ee4cecf--