---------------------
PatchSet 5054 
Date: 2007/07/12 05:01:22
Author: amosjeffries
Branch: docs
Tag: (none) 
Log:
Remove some duplicated text.

Members: 
	src/fs/FileSystems.dox:1.1.2.2->1.1.2.3 

Index: squid3/src/fs/FileSystems.dox
===================================================================
RCS file: /cvsroot/squid-sf//squid3/src/fs/Attic/FileSystems.dox,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- squid3/src/fs/FileSystems.dox	12 Jul 2007 04:45:40 -0000	1.1.2.2
+++ squid3/src/fs/FileSystems.dox	12 Jul 2007 05:01:22 -0000	1.1.2.3
@@ -3,26 +3,6 @@
 \ingroup Modules
 
 \section Introduction Introduction
-
-\par
-	Traditionally, Squid has always used the Unix filesystem (\link UFS UFS\endlink)
-	to store cache objects on disk. Over the years, the poor performance of UFS has
-	become very obvious. In most cases, UFS limits Squid to about 30-50 requests per
-	second. Our work indicates that the poor performance is mostly due to the
-	synchronous nature of open() and unlink() system calls, and perhaps thrashing of
-	inode/buffer caches.
-
-\par
-	We want to try out our own, customized filesystems with Squid. In order to do that,
-	we need a well-defined interface for the bits of Squid that access the permanent
-	storage devices. We also require tighter control of the replacement policy by each
-	storage module, rather than a single global replacement policy.
-
-
-\todo DOCS: pull remaining generic FS documentation into here fully.
-
-
-\section Introduction Introduction
 \par
 	Traditionally, Squid has always used the Unix filesystem (\link UFS UFS\endlink)
 	to store cache objects on disk.  Over the years, the