Date: Tue, 24 Feb 2015 11:36:46 +0000 From: Tim Borgeaud <timothy.borgeaud@framestore.com> To: freebsd-net@freebsd.org Cc: Mark Hills <mark.hills@framestore.com> Subject: NFS: kernel modules (loading/unloading) and scheduling Message-ID: <CADqOPxsJ4Sjt_u6%2Bh5B8sFWFzOHQA28E69H0LnxxZg1UPeup7g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi FreeBSD folks, here at Framestore Mark Hills (cc'd) has been looking at how NFS servers schedule/prioritize incoming requests with a view towards a client/user 'fair share' of a service. We are taking a look at trying out some simple approaches of queuing up and handling requests. There are, obviously, various matters to deal with here, and several complications. However, an initial consideration is how we might best develop and test with the FreeBSD kernel code. Specifically, whether we would be able to unload and reload NFS related kernel modules, or whether there are any other alternatives. It looks like there are several modules involved such as krpc, nfssvc, nfscommon, nfslock, which we can build outside of the kernel itself, but which do not all support unloading. Not being able to reload a module does seem to present a hurdle to development and, therefore, I'd like to know how FreeBSD developers have managed development of the NFS functionality and what approaches may be recommended. It occurs to me that it would be possible for us to consider adding some ability to unload some of these modules, even if it were not suitable for anything other than development. Therefore, an extension of my main, more general, query is to ask how straightforward or fundamentally difficult this may be (for the NFS modules)? Thanks very much -- Tim Borgeaud Systems Developer =E2=80=8BFramestore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqOPxsJ4Sjt_u6%2Bh5B8sFWFzOHQA28E69H0LnxxZg1UPeup7g>