c1a1692e09
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. |
||
---|---|---|
.. | ||
3RDPARTY | ||
BRANCHES | ||
BUILDING.mdoc | ||
CHANGES | ||
CHANGES.prev | ||
HACKS | ||
LAST_MINUTE | ||
README.files | ||
RESPONSIBLE | ||
ROADMAP | ||
TODO | ||
TODO.i18n | ||
TODO.kqueue | ||
TODO.nits |
# $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.