All of lore.kernel.org
 help / color / mirror / Atom feed
From: Menyhart Zoltan <Zoltan.Menyhart@bull.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Patch: making DLM more robust
Date: Tue, 30 Nov 2010 17:57:50 +0100	[thread overview]
Message-ID: <4CF52D0E.2020800@bull.net> (raw)
In-Reply-To: <20101123171508.GC30147@redhat.com>

Hi,

An easy first step to make DLM more robust can be adding a time out protection
to the lock space cration operation, while waiting for a "dlm_controld" action.
A new memeber "ci_dlm_controld_secs" is added to "dlm_config" to set up time out
in seconds, DEFAULT_DLM_CTRL_SECS is 5 seconds.

At the same time, signals can be enabled and handled, too.

DLM_USER_CREATE_LOCKSPACE will be able to return new error codes:
-EINTR or -ETIMEDOUT.

Could you please tell me why the signals are blocked within "device_write()"?
I think it is safe to allow signals, surely in your original code sequences
waiting in an uninterruptible way.

BTW "sigprocmask()" already contains "recalc_sigpending()".

  out_sig:
     sigprocmask(SIG_SETMASK, &tmpsig, NULL);
     recalc_sigpending();


Thanks,

Zoltan Menyhart
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diff2
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20101130/d22fbbe9/attachment.ksh>

  parent reply	other threads:[~2010-11-30 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 16:31 [Cluster-devel] "->ls_in_recovery" not released Menyhart Zoltan
2010-11-22 17:34 ` David Teigland
2010-11-23 14:58   ` Menyhart Zoltan
2010-11-23 17:15     ` David Teigland
2010-11-24 16:13       ` Menyhart Zoltan
2010-11-24 20:29         ` David Teigland
2010-11-30 16:57       ` Menyhart Zoltan [this message]
2010-11-30 17:30         ` [Cluster-devel] Patch: making DLM more robust David Teigland
2010-12-01  9:23           ` Menyhart Zoltan
2010-12-01 17:27             ` David Teigland

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=4CF52D0E.2020800@bull.net \
    --to=zoltan.menyhart@bull.net \
    /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.