From owner-svn-src-all@FreeBSD.ORG Fri May 1 11:46:25 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EB5BC94; Fri, 1 May 2015 11:46:25 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D8011D13; Fri, 1 May 2015 11:46:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t41BkO9e094165; Fri, 1 May 2015 11:46:24 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t41BkOOY094164; Fri, 1 May 2015 11:46:24 GMT (envelope-from bapt@FreeBSD.org) Message-Id: <201505011146.t41BkOOY094164@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f From: Baptiste Daroussin Date: Fri, 1 May 2015 11:46:24 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r282297 - head/share/doc/papers/bufbio X-SVN-Group: head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2015 11:46:25 -0000 Author: bapt Date: Fri May 1 11:46:24 2015 New Revision: 282297 URL: https://svnweb.freebsd.org/changeset/base/282297 Log: Fix font issues Submitted by: heirloom doctools upstream Modified: head/share/doc/papers/bufbio/bio.ms Modified: head/share/doc/papers/bufbio/bio.ms ============================================================================== --- head/share/doc/papers/bufbio/bio.ms Fri May 1 05:11:14 2015 (r282296) +++ head/share/doc/papers/bufbio/bio.ms Fri May 1 11:46:24 2015 (r282297) @@ -40,7 +40,7 @@ This paper contains the road-map for a s FreeBSD, which will support these facilities. .AE .NH -The miseducation of \fCstruct buf\fP. +The miseducation of \f(CW.)struct buf\fP. .PP To fully appreciate the topic, I include a little historic overview of struct buf, it is a most enlightening case of not exactly bit-rot @@ -51,7 +51,7 @@ memory is was introduced into UNIX, all to a struct buf. In the 6th edition sources, as printed in Lions Book, struct buf looks like this: .DS -.ft C +.ft CW .ps -1 struct buf { @@ -95,7 +95,7 @@ aspect and only a few fields relate excl If we step forward to the BSD 4.4-Lite-2 release, struct buf has grown a bit here or there: .DS -.ft C +.ft CW .ps -1 struct buf { LIST_ENTRY(buf) b_hash; /* Hash chain. */ @@ -144,7 +144,7 @@ aspect, link buffers to the VM system, p .PP By the time we get to FreeBSD 3.0 more stuff has grown on struct buf: .DS -.ft C +.ft CW .ps -1 struct buf { LIST_ENTRY(buf) b_hash; /* Hash chain. */ @@ -215,7 +215,7 @@ and Vinum. They all basically do the sa a logical space to a physical space, and the mappings they perform can be 1:1 or 1:N. \** .FS -It is interesting to note that Lions in his comments to the \fCrkaddr\fP +It is interesting to note that Lions in his comments to the \f(CW.)rkaddr\fP routine (p. 16-2) writes \fIThe code in this procedure incorporates a special feature for files which extend over more than one disk drive. This feature is described in the UPM Section "RK(IV)". Its @@ -258,7 +258,7 @@ limited extent diskslice/label, which need only the I/O aspect, not the vnode, caching or VM linkage. .IP .I -The I/O aspect of struct buf should be put in a separate \fCstruct bio\fP. +The I/O aspect of struct buf should be put in a separate \f(CW.)struct bio\fP. .R .NH 1 Implications for future struct buf improvements @@ -296,7 +296,7 @@ Anything that could be added to or done the I/O aspect of struct buf can also be added to or done with the I/O aspect if it lives in a new "struct bio". .NH 1 -Implementing a \fCstruct bio\fP +Implementing a \f(CW.)struct bio\fP .PP The first decision to be made was who got to use the name "struct buf", and considering the fact that it is the I/O aspect which gets separated @@ -344,7 +344,7 @@ Definition of struct bio .PP With the cleanup of b_flags in place, the definition of struct bio looks like this: .DS -.ft C +.ft CW .ps -1 struct bio { u_int bio_cmd; /* I/O operation. */ @@ -375,7 +375,7 @@ Definition of struct buf After adding a struct bio to struct buf and the fields aliased into it struct buf looks like this: .DS -.ft C +.ft CW .ps -1 struct buf { /* XXX: b_io must be the first element of struct buf for now /phk */ @@ -424,7 +424,7 @@ And can be found at http://phk.freebsd.d .FE and consists mainly of systematic substitutions like these .DS -.ft C +.ft CW s/struct buf/struct bio/ s/b_flags/bio_flags/ s/b_bcount/bio_bcount/