NetBSD/doc
reinoud c1a1692e09 Modify description of the reinoud-bufcleanup experiment branch:
Branch:      reinoud-bufcleanup
Description: implement and evaluate struct buf usage cleanup strategies.
             Ideas currently in mind (preference for b):
             a)
                 1. use of bio_ops per buffer.
                 2. allow chaining/overloading of functions in bio_ops
                    and provide some private context.
                 3. extend the bio_ops with commenly used functionality
                    like pending action counting, custom context passing,
                    last minute processing of buffer data, buffer cache
                    etc.
                 4. investigate the use of the kcont()
                    continuation-passing framework for async io
                    completion notification for bufs
                 ...
             b)
                 1. all sequencing use of B_CALL replaced by
                    device-threads, if possible generic code around BUFQ
                 2. possibly use kcont() for async IO finished signalling
                 3. counter of pending and queued actions requestable
                    by IOCTL interface?
                 4. implement `last minute buffer fixup' calls and maybe
                    even finished I/O calls as vnode operations
                 ...
Status:         Active
Start Date:     Thu Mar 15 2007
End Date:
Base Tag:       reinoud-bufcleanup-base
Maintainer:     Reinoud Zandijk <reinoud@NetBSD.org>
Scope:          src/sys and src/common
Notes:          Used as expiriment sandbox and if successful hopefully one day
                to be intergrated.
2007-03-17 17:24:44 +00:00
..
3RDPARTY new openssh. 2007-03-10 23:07:11 +00:00
BRANCHES Modify description of the reinoud-bufcleanup experiment branch: 2007-03-17 17:24:44 +00:00
BUILDING.mdoc Try to clarify the description of build.sh -m mach. 2007-01-27 11:47:36 +00:00
CHANGES Remove previous item... 2007-03-15 00:36:52 +00:00
CHANGES.prev netccit -> netccitt 2007-02-23 19:11:13 +00:00
HACKS fix a typo and remove one that's been removed from the code. 2007-01-08 17:41:21 +00:00
LAST_MINUTE Remove 1.6-specific issues; they're now covered by the LAST_MINUTE on 2002-09-23 07:52:18 +00:00
README.files Fix a URL. From OKANO Takayoshi in PR 33001. 2006-03-09 18:07:53 +00:00
RESPONSIBLE Complete rename of hfsp to hfs, requested by thorpej. 2007-03-06 11:28:44 +00:00
ROADMAP Sync scheduler with reality: 2007-03-11 21:05:57 +00:00
TODO * make clear what "window" is 2005-09-27 20:15:15 +00:00
TODO.i18n PR/30809 added manpages of wcswcs(3) and wcscoll(3), wcsxfrm(3) 2006-10-13 17:28:09 +00:00
TODO.kqueue test-compiled evbsh5 CAYMAN and SIMULATOR, and pc532 GENERIC, remove from TODO 2003-12-08 06:43:55 +00:00
TODO.nits RPC kqueue project done. 2005-10-13 23:41:03 +00:00

#	$NetBSD: README.files,v 1.3 2006/03/09 18:07:53 wiz Exp $

What's in this directory:

CHANGES		Changes between the XXX.XXX-1 and XXX.XXX releases.

CHANGES.prev	Changes in previous NetBSD releases.

LAST_MINUTE	Last minute changes and notes about the release.

README.files	This file.

patches/	Post-release binary code patches.

shared/		Binary sets shared between multiple ports.

source/		Source code.

source/sets/	Source distribution sets; see below.

source/patches/	Post-release source code patches.



In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD XXX.XXX has a binary distribution.  The contents of each
architecture's directory are described in an "INSTALL" file found in
that directory.

The most recent list of mirror sites for NetBSD is viewable at the URL:

	http://www.NetBSD.org/mirrors/

If you are receiving this distribution on a CD set, some files and
subdirectories may be on a separate disc; read all README files for more
information.

See http://www.NetBSD.org/Misc/crypto-export.html for the formal status of
the exportability out of the United States of some pieces of the
distribution tree containing cryptographic software.  If you export these
bits and the above document says you should not do so, it's your fault,
not ours.