From: Christoph Hellwig <hch@infradead.org>
To: "Denis V. Lunev" <den@sw.ru>
Cc: Christoph Hellwig <hch@infradead.org>,
"Denis V. Lunev" <den@openvz.org>,
trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org,
xemul@openvz.org, devel@openvz.org
Subject: Re: [PATCH] [NFS]: Lock daemon start/stop rework.
Date: Wed, 6 Feb 2008 04:13:18 +0000 [thread overview]
Message-ID: <20080206041318.GA6589@infradead.org> (raw)
In-Reply-To: <47A17D50.4000409@sw.ru>
On Thu, Jan 31, 2008 at 10:48:32AM +0300, Denis V. Lunev wrote:
> Christoph Hellwig wrote:
> > 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.
> >
> >
> where can I have to look them? :)
The lastest version was just posted on the linux-nfs list:
http://marc.info/?l=linux-nfs&m=120224048613393&w=2
next prev parent reply other threads:[~2008-02-06 4:13 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
2008-01-31 7:48 ` Denis V. Lunev
2008-02-06 4:13 ` Christoph Hellwig [this message]
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=20080206041318.GA6589@infradead.org \
--to=hch@infradead.org \
--cc=den@openvz.org \
--cc=den@sw.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.