Date: Mon, 22 Nov 2010 16:29:27 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-fs@freebsd.org Cc: Ivan Voras <ivoras@freebsd.org> Subject: Re: preferred kernel upcall method to master nfsd Message-ID: <201011221629.27166.jhb@freebsd.org> In-Reply-To: <ice0pk$tff$1@dough.gmane.org> References: <1121329727.428865.1290431972028.JavaMail.root@erie.cs.uoguelph.ca> <201011220928.24386.jhb@freebsd.org> <ice0pk$tff$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, November 22, 2010 10:04:27 am Ivan Voras wrote: > On 11/22/10 15:28, John Baldwin wrote: > > On Monday, November 22, 2010 8:19:32 am Rick Macklem wrote: > >> Hi, > >> > >> The experimental NFSv4 server in the kernel needs to tell the master nfsd when > >> to make a backup copy of the stable restart file. I know how to do this using a > >> signal, but is there a better/preferred way under FreeBSD-current? > > > > A signal sounds like the simplest approach to me. > > Signals work for processes inside the kernel? How? The scheduler > preempts them and does magic when deciding where to continue running them? nfsd is a user process. I suspect that when it receives a signal it falls out of nfssvc() with EINTR and handles saving the restart file in userland. Is that close to the process Rick or does you need to send a signal between threads that are exclusively within the kernel? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011221629.27166.jhb>