src-test2/sys/gnu/ext2fs/ext2_readwrite.c, branch release/5.2.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-01-10T05:53:29Z

'RELENG_5_2_0_RELEASE'. This commit was manufactured to restore the state of the 5.2-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

Remove register keyword.

2002-05-16T19:43:28Z

Complete the separation of ext2fs from ufs by copying the remaining

2002-05-16T19:08:03Z

shared code and converting all ufs references. Originally it may have made sense to share common features between the two filesystems, but recently it has only caused problems, the UFS2 work being the final straw. All UFS_* indirect calls are now direct calls to ext2_* functions, and ext2fs-specific mount and inode structures have been introduced.

KSE Milestone 2

2001-09-12T08:38:13Z

Note ALL MODULES MUST BE RECOMPILED make the kernel aware that there are smaller units of scheduling than the process. (but only allow one thread per process at this time). This is functionally equivalent to teh previousl -current except that there is a thread associated with each process. Sorry john! (your next MFC will be a doosie!) Reviewed by: peter@freebsd.org, dillon@freebsd.org X-MFC after: ha ha ha ha

Grab the process lock while calling psignal and before calling psignal.

2001-03-07T03:37:06Z

Proc locking, mostly protecting p_ucred while obtaining additional

2001-01-23T22:41:15Z

references.

Avoid a data-consistency race between write() and mmap()

2000-12-17T23:57:05Z

by ensuring that newly allocated blocks are zerod. The race can occur even in the case where the write covers the entire block. Reported by: Sven Berkvens , Marc Olzheim

Change the write-behind code to take more care when starting

2000-04-02T00:55:28Z

async I/O's. The sequential read heuristic has been extended to cover writes as well. We continue to call cluster_write() normally, thus blocks in the file will still be reallocated for large (but still random) I/O's, but I/O will only be initiated for truely sequential writes. This solves a number of annoying situations, especially with DBM (hash method) writes, and also has the side effect of fixing a number of (stupid) benchmarks. Reviewed-by: mckusick

More removals of vnode->v_lastr, replaced by preexisting seqcount

1999-09-20T23:27:58Z

heuristic to detect sequential operation. VM-related forced clustering code removed from ufs in preparation for a commit to vm/vm_fault.c that does it more generally. Reviewed by: David Greenman , Alan Cox

Don't set IN_ACCESS for requests to read 0 bytes or for unsuccessful reads.

1999-07-25T02:56:17Z

Translated from: similar fixes in ufs_readwrite.c rev.1.61. Things are simpler (but annoyingly different) here because there are no vm optimisations.