Background writes are entirely an FFS/Softupdates thing.

Give FFS vnodes a specific bufwrite method which contains all the
background write stuff and then calls into the default bufwrite()
for the rest of the job.

Remove all the background write related stuff from the normal bufwrite.

This drags the softdep_move_dependencies() back into FFS.

Long term, it is worth looking at simply copying the data into
allocated memory and issuing the bio directly and not create the
"shadow buf" in the first place (just like copy-on-write is done
in snapshots for instance).  I don't think we really gain anything
but complexity from doing this with a buf.

1 files changed, 0 insertions, 8 deletions

diff --git a/sys/sys/buf.h b/sys/sys/buf.h
index 25a9133..f80316c 100644
--- a/sys/sys/buf.h
+++ b/sys/sys/buf.h
@@ -64,7 +64,6 @@ extern struct bio_ops {
 	void	(*io_start)(struct buf *);
 	void	(*io_complete)(struct buf *);
 	void	(*io_deallocate)(struct buf *);
-	void	(*io_movedeps)(struct buf *, struct buf *);
 	int	(*io_countdeps)(struct buf *, int);
 } bioops;
 
@@ -436,13 +435,6 @@ buf_deallocate(struct buf *bp)
 	BUF_LOCKFREE(bp);
 }
 
-static __inline void
-buf_movedeps(struct buf *bp, struct buf *bp2)
-{
-	if (bioops.io_movedeps)
-		(*bioops.io_movedeps)(bp, bp2);
-}
-
 static __inline int
 buf_countdeps(struct buf *bp, int i)
 {