linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christine Caulfield <ccaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] clvmd on openais
Date: Wed, 23 Apr 2008 10:54:22 +0100	[thread overview]
Message-ID: <480F074E.40903@redhat.com> (raw)
In-Reply-To: <1cafab770804230225l6dabdd65na69df87466a81ed6@mail.gmail.com>

Xinwei Hu wrote:
> 2008/4/23, Christine Caulfield <ccaulfie@redhat.com>:
>> Xinwei Hu wrote:
>>  > 2008/4/23, Christine Caulfield <ccaulfie@redhat.com>:
>>  >> Xinwei Hu wrote:
>>  >>  > Hi all,
>>  >>  >   clvmd-openais.c uses saLckResourceLockAsync and
>>  >>  > saLckResourceUnlockAsync. But they then pthread_cond_wait the lock
>>  >>  > operation to finished.
>>  >>  >
>>  >>  >   Since we have to wait, why not switch to use saLckResourceLock and
>>  >>  > saLckResourceUnlock directly ? Are there any reasons behind this ?
>>  >>  >
>>  >>
>>  >>
>>  >> It's mainly because the code was copied and editted from the other
>>  >>  cluster systems, I think :-)
>>  > Then I propose this patch to switch over. ;)
>>
>>
>>
>> Thanks, but that patch seems to have got corrupted or something, it
>>  doesn't apply to head of CVS. can you send it again please ?
>>
>>
>>  Hunk #3 FAILED at 295.
>>  Hunk #4 succeeded at 315 (offset -8 lines).
>>  Hunk #6 succeeded at 478 (offset -8 lines).
>>  patch: **** malformed patch at line 161: @@ -590,15 +536,13 @@
>>
> Take 2.
> Against CVS head now. Please help to review ;)


That looks good to me and it tests out OK.

It's now in CVS, thank you very much.

-- 

Chrissie

      reply	other threads:[~2008-04-23  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  7:25 [linux-lvm] clvmd on openais Xinwei Hu
2008-04-23  7:42 ` Christine Caulfield
2008-04-23  8:10   ` Xinwei Hu
2008-04-23  9:12     ` Christine Caulfield
2008-04-23  9:25       ` Xinwei Hu
2008-04-23  9:54         ` Christine Caulfield [this message]

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=480F074E.40903@redhat.com \
    --to=ccaulfie@redhat.com \
    --cc=linux-lvm@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).