[src/trunk]: src/doc/roadmaps note that the first step on the buffercache is ...

[dholland <dholland%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/0df39d6f700e
branches:  trunk
changeset: 350623:0df39d6f700e
user:      dholland <dholland%NetBSD.org@localhost>
date:      Sat Jan 14 20:50:15 2017 +0000

description:
note that the first step on the buffercache is to disentangle the buffer
cache and the buffer I/O path.

diffstat:

 doc/roadmaps/mess |  6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diffs (20 lines):

diff -r 747a837a0ae1 -r 0df39d6f700e doc/roadmaps/mess
--- a/doc/roadmaps/mess Sat Jan 14 20:49:24 2017 +0000
+++ b/doc/roadmaps/mess Sat Jan 14 20:50:15 2017 +0000
@@ -1,4 +1,4 @@
-$NetBSD: mess,v 1.1 2017/01/13 10:14:58 dholland Exp $
+$NetBSD: mess,v 1.2 2017/01/14 20:50:15 dholland Exp $
 
 NetBSD Messes and Tentacular Horrors Roadmap
 ============================================
@@ -77,6 +77,10 @@
 reflects non-current assumptions about the way file system buffers
 should work.
 
+The first step on this is to disentangle the buffer cache
+(buffercache(9)) from the buffer I/O path (bufferio(9)) -- right now
+they both abusively share the same struct buf.
+
  - As of January 2017 nobody is currently working on this.
  - There is currently no clear timeframe or release target.
  - Contact dholland for further information.