BMC/Intel-BMC/linux.git/fs/nfs/blocklayout/blocklayout.h, branch dev

pnfs/blocklayout: in-kernel GETDEVICEINFO XDR parsing

2014-09-12T17:33:50+00:00

This patches moves parsing of the GETDEVICEINFO XDR to kernel space, as well as the management of complex devices. The reason for that is we might have multiple outstanding complex devices after a NOTIFY_DEVICEID4_CHANGE, which device mapper or md can't handle as they claim devices exclusively. But as is turns out simple striping / concatenation is fairly trivial to implement anyway, so we make our life simpler by reducing the reliance on blkmapd. For now we still use blkmapd by feeding it synthetic SIMPLE device XDR to translate device signatures to device numbers, but in the long runs I have plans to eliminate it entirely. Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

pnfs/blocklayout: move all rpc_pipefs related code into a single file

2014-09-12T17:33:50+00:00

Create a file to house all the rpc_pipefs boilerplate code instead of sprinkling it over a few files. Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

pnfs/blocklayout: move extent processing to blocklayout.c

2014-09-12T17:33:49+00:00

This isn't device(id) related, so move it into the main file. Simple move for now, the next commit will clean it up a bit. Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

pnfs/blocklayout: allocate separate pages for the layoutcommit payload

2014-09-12T17:22:45+00:00

Instead of overflowing the XDR send buffer with our extent list allocate pages and pre-encode the layoutupdate payload into them. We optimistically allocate a single page use alloc_page and only switch to vmalloc when we have more extents outstanding. Currently there is only a single testcase (xfstests generic/113) which can reproduce large enough extent lists for this to occur. Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

pnfs/blocklayout: use the device id cache

2014-09-10T19:47:04+00:00

Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

pnfs/blocklayout: rewrite extent tracking

2014-09-10T19:47:03+00:00

Currently the block layout driver tracks extents in three separate data structures: - the two list of pnfs_block_extent structures returned by the server - the list of sectors that were in invalid state but have been written to - a list of pnfs_block_short_extent structures for LAYOUTCOMMIT All of these share the property that they are not only highly inefficient data structures, but also that operations on them are even more inefficient than nessecary. In addition there are various implementation defects like: - using an int to track sectors, causing corruption for large offsets - incorrect normalization of page or block granularity ranges - insufficient error handling - incorrect synchronization as extents can be modified while they are in use This patch replace all three data with a single unified rbtree structure tracking all extents, as well as their in-memory state, although we still need to instance for read-only and read-write extent due to the arcane client side COW feature in the block layouts spec. To fix the problem of extent possibly being modified while in use we make sure to return a copy of the extent for use in the write path - the extent can only be invalidated by a layout recall or return which has to wait until the I/O operations finished due to refcounts on the layout segment. The new extent tree work similar to the schemes used by block based filesystems like XFS or ext4. Signed-off-by: Christoph Hellwig Signed-off-by: Trond Myklebust

NFS: Enabling v4.2 should not recompile nfsd and lockd

2013-11-19T21:20:40+00:00

When CONFIG_NFS_V4_2 is toggled nfsd and lockd will be recompiled, instead of only the nfs client. This patch moves a small amount of code into the client directory to avoid unnecessary recompiles. Signed-off-by: Anna Schumaker Signed-off-by: Trond Myklebust

make blkdev_put() return void

2013-05-07T06:16:31+00:00

same story as with the previous patches - note that return value of blkdev_close() is lost, since there's nowhere the caller (__fput()) could return it to. Signed-off-by: Al Viro

pnfsblock: cleanup nfs4_blkdev_get

2012-10-08T23:32:40+00:00

It is not needed at all and it is messing with return values... Reported-by: Wei Yongjun Signed-off-by: Peng Tao Signed-off-by: Trond Myklebust

pnfsblock: fix partial page buffer wirte

2012-10-01T22:38:24+00:00

If applications use flock to protect its write range, generic NFS will not do read-modify-write cycle at page cache level. Therefore LD should know how to handle non-sector aligned writes. Otherwise there will be data corruption. Cc: stable Signed-off-by: Peng Tao Signed-off-by: Trond Myklebust