Messages in this thread | | | Date | Thu, 17 Nov 2005 00:35:43 -0500 | From | Xin Zhao <> | Subject | nfs3 implementation issue? |
| |
In nfs/nfs3proc.c: nfs3_read_done(), I saw the following line:
struct nfs_write_data *data = (struct nfs_write_data *) task->tk_calldata;
I don't know why the tk_calldata is regarded as nfs_write_data instead of nfs_read_data. When this rpc call is set up, we put task->tk_calldata as a nfs_read_data object, why will it become a nfs_write_data after the rpc call is done?
Can someone explain this a little bit?
Thanks!
Xin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |