The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	hch@infradead.org
Subject: Re: [PATCH] lockd: convert reclaimer thread to kthread interface
Date: Tue, 04 Nov 2008 14:26:21 -0500	[thread overview]
Message-ID: <1225826781.30407.11.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20081104134235.0382c873@tleilax.poochiereds.net>

On Tue, 2008-11-04 at 13:42 -0500, Jeff Layton wrote:
> While we're on the subject of signals...
> 
> Do you have any thoughts/objections to just making the reclaimer thread
> ignore them altogether? That would simplify the code a bit.

How does the administrator then get out of the situation where the
server dies (permanently) in the middle of a reclaim?

Forced unmounts won't help here, since they only signal the NFS
requests, and are in any case per-filesystem, not per-server.

I suppose one could use soft RPC calls, but what should the retry policy
be for that case?

Trond


  reply	other threads:[~2008-11-04 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 11:15 [PATCH] lockd: convert reclaimer thread to kthread interface Jeff Layton
2008-11-03 21:12 ` Andrew Morton
2008-11-03 22:28   ` Jeff Layton
2008-11-04  0:19   ` Jeff Layton
2008-11-04  3:20     ` Trond Myklebust
2008-11-04 12:41     ` Trond Myklebust
2008-11-04 18:42       ` Jeff Layton
2008-11-04 19:26         ` Trond Myklebust [this message]
2008-11-04 19:46           ` Jeff Layton
2008-11-04 20:17             ` Trond Myklebust
2008-11-04 20:38               ` Jeff Layton
  -- strict thread matches above, loose matches on Subject: below --
2008-11-05 20:17 Jeff Layton

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=1225826781.30407.11.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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