From: Christoph Hellwig <hch@infradead.org>
To: "Denis V. Lunev" <den@openvz.org>
Cc: trond.myklebust@fys.uio.no, hch@infradead.org,
linux-kernel@vger.kernel.org, xemul@openvz.org, devel@openvz.org
Subject: Re: [PATCH] [NFS]: Lock daemon start/stop rework.
Date: Thu, 31 Jan 2008 03:33:20 +0000 [thread overview]
Message-ID: <20080131033320.GA15067@infradead.org> (raw)
In-Reply-To: <1201693294-11460-1-git-send-email-den@openvz.org>
On Wed, Jan 30, 2008 at 02:41:34PM +0300, Denis V. Lunev wrote:
> The pid of the locking daemon can be substituted with a task struct
> without a problem. Namely, the value if filled in the context of the lockd
> thread and used in lockd_up/lockd_down.
>
> It is possible to save task struct instead and use it to kill the process.
> The safety of this operation is guaranteed by the RCU, i.e. task can't
> disappear without passing a quiscent state.
We have a patch series pending on the nfs list that does this plus a lot
more in the area.
next prev parent reply other threads:[~2008-01-31 3:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 11:41 [PATCH] [NFS]: Lock daemon start/stop rework Denis V. Lunev
2008-01-31 3:33 ` Christoph Hellwig [this message]
2008-01-31 7:48 ` Denis V. Lunev
2008-02-06 4:13 ` Christoph Hellwig
2008-03-11 13:46 ` Pavel Emelyanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080131033320.GA15067@infradead.org \
--to=hch@infradead.org \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox