4014bd401f
Tested under CHAOS4.2, RHEL5, SLES11, and FC11 (all x86_64) Features: Honor spa_mode() when opening the block device. Previously this was ignored and devices were always opened read/write. Integrated DKIOCFLUSHWRITECACHE zio operation with linux WRITE_BARRIER for kernels post 2.6.24 where empty bio requests are supported. For earlier kernels ENOTSUP is returned and no barriers are performed. If RHEL5 based kernels are intended to be supported long term we may need make use of the old akward API. With the addition of WRITE_BARRIER support all writes which were WRITE_SYNC can now be safely made WRITE bios. They will now take advantage of aggregation in the elevator and improved write performance is likely. Notice the ZIO_FLAG_SPECULATIVE flag and pass along the hint to the elevator by using READA instead of READ. This provides the elevator the ability to prioritize the real READs ahead of the speculative IO if needed. Implement an initial version of vdev_disk_io_done() which in the case of an EIO error triggers a media change check. If it determines a media change has occured we fail the device and remove it from the config. This logic I'm sure can be improved further but for now it is an improvement over the VERIFY() that no error will ever happen. APIs: 2.6.22 API change Unused destroy_dirty_buffers arg removed from prototype. 2.6.24 API change Empty write barriers are now supported and we should use them. 2.6.24 API change Size argument dropped from bio_endio and bi_end_io, because the bi_end_io is only called once now when the request is complete. There is no longer any need for a size argument. This also means that partial IO's are no longer possibe and the end_io callback should not check bi->bi_size. Finally, the return type was updated to void. 2.6.28 API change open/close_bdev_excl() renamed to open/close_bdev_exclusive(). 2.6.29 API change BIO_RW_SYNC renamed to BIO_RW_SYNCIO. |
||
|---|---|---|
| cmd | ||
| config | ||
| doc | ||
| lib | ||
| module | ||
| scripts | ||
| .topdeps | ||
| .topmsg | ||
| AUTHORS | ||
| COPYING | ||
| COPYRIGHT | ||
| ChangeLog | ||
| DISCLAIMER | ||
| GIT | ||
| META | ||
| Makefile.am | ||
| OPENSOLARIS.LICENSE | ||
| README | ||
| TODO | ||
| ZFS.RELEASE | ||
| autogen.sh | ||
| configure.ac | ||
| zfs-modules.spec.in | ||
| zfs.spec.in | ||
| zfs_unconfig.h | ||
README
============================ ZFS KERNEL BUILD ============================
1) Build the SPL (Solaris Porting Layer) module which is designed to
provide many Solaris APIs in the Linux kernel which are needed
by ZFS. To build the SPL:
tar -xzf spl-x.y.z.tgz
cd spl-x.y.z
./configure --with-linux=<kernel src>
make
make check <as root>
2) Build ZFS, this port is based on build specified by the ZFS.RELEASE
file. You will need to have both the kernel and SPL source available.
To build ZFS for use as a Linux kernel module.
tar -xzf zfs-x.y.z.tgz
cd zfs-x.y.z
./configure --with-linux=<kernel src> \
--with-spl=<spl src>
make
make check <as root>
============================ ZPIOS TEST SUITE ============================
3) Provided is an in-kernel test application called zpios which can be
used to simulate a parallel IO load. It may be used as a stress
or performance test for your configuration. To simplify testing
scripts provided in the scripts/ directory which provide a few
pre-built zpool configurations and zpios test cases. By default
'make check' as root will run a simple test against several small
loopback devices created in /tmp/.
cd scripts
./zfs.sh # Load the ZFS/SPL modules
./zpios.sh -c lo-raid0.sh -t tiny -v # Tiny zpios loopback test
./zfs.sh -u # Unload the ZFS/SPL modules
Enjoy,
Brian Behlendorf <behlendorf1@llnl.gov>