On Fri, Dec 19, 2008 at 10:50:27PM +0800, lioupayphone wrote: > >I hope this helps... > :-) thank you very much. i think your comments are very clear and very > helpful for me. but i still think rpc.mountd is somewhat complex. we > all know that a daemon in user-mode is likely to be killed. rpc.mountd > is no exception. once rpc.mountd was killed, there are no chance for > the export_table to be updated via upcall. > > It cannot be denied that putting the etab into kernel mode is wastful > for memory. but i still think it is an easy and stable method. Even with the export table in memory, rpc.mountd will still be needed for ip-address lookup (e.g. if a filesystem is exported to *.umich.edu, and the kernel gets an rpc from 141.211.133.1, then it needs to do an upcall to determine whether the given ip address matches that wildcard). However it's true that there might be advantages to having the export table in-kernel. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
