Active Block I/O Scheduling System (ABISS), version 8

The Active Block I/O Scheduling System (ABISS) is an extension of the
hard-disk storage subsystem of Linux, whose main purpose is to provide
a guaranteed reading and (eventually) writing bit rate to applications.

ABISS is conducted by Philips Research in Eindhoven, the Netherlands
(see http://www.research.philips.com/technologies/storage/inde...).

http://abiss.sourceforge.net/abiss-8.tar.gz
md5sum 74199f051c4ef31e38561c695c549813
sha1sum 0f5f04593eb998a41e5184ede503dfffee8d8a9d

This is an important maintenance release, which fixes a bug that could
cause file system corruption. The highlights:

 - if ABISS couldn't keep up while writing, pages could be marked for
   delayed allocation while locked, badly confusing the rest of the
   kernel

 - rdrt ("ReaD Real-Time") is now called rwrt ("Read/Write Real-Time")

 - rwrt can now invoked without the read/write size argument, which is
   convenient if we just want to verify sequence numbers

 - communication with abissd used to fail if the file being opened was
   badly fragmented (such that the list of fragments was too large to
   send). Now, the message size is adjusted dynamically, allowing for
   much larger messages.

 - added an experimental mechanism for making FAT make contiguous
   allocations larger than one cluster. This is activated with the
   mount option  space=N  where N is the number of kilobytes we want
   to allocate contiguously. (E.g. if writing two 1MB files in
   parallel on a file system with a cluster size of 4 kB, you'd get
   about 256 fragments in each. With space=64, there would be only
   16 fragments.)

For additional information, please have a look at
http://abiss.sourceforge.net/

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner@almesberger.net /
/_http://www.almesberger.net/______________________________...
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html