public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/lib/locking cluster_locking.c Date: Wed, 02 Feb 2011 23:57:00 -0000 [thread overview] Message-ID: <20110202235748.21698.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2011-02-02 23:57:48 Modified files: lib/locking : cluster_locking.c Log message: a few more comments Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/cluster_locking.c.diff?cvsroot=lvm2&r1=1.52&r2=1.53 --- LVM2/lib/locking/cluster_locking.c 2011/02/02 23:39:39 1.52 +++ LVM2/lib/locking/cluster_locking.c 2011/02/02 23:57:48 1.53 @@ -342,10 +342,14 @@ * VG locks are just that: locks, and have no side effects * so we only need to do them on the local node because all * locks are cluster-wide. + * * Also, if the lock is exclusive it makes no sense to try to * acquire it on all nodes, so just do that on the local node too. - * One exception, is that P_ locks (except VG_SYNC_NAMES) /do/ get - * distributed across the cluster because they might have side-effects. + * + * P_ locks /do/ get distributed across the cluster because they might + * have side-effects. + * + * SYNC_NAMES and VG_BACKUP use the VG name directly without prefix. */ if (clvmd_cmd == CLVMD_CMD_SYNC_NAMES) { if (flags & LCK_LOCAL)
next reply other threads:[~2011-02-02 23:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-02 23:57 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-12-08 18:19 agk 2011-11-30 17:02 mornfall 2011-02-01 17:31 jbrassow 2010-11-29 11:13 zkabelac 2009-12-09 18:28 mbroz 2009-12-09 18:16 mbroz 2008-12-16 12:30 wysochanski 2006-05-12 13:33 agk
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=20110202235748.21698.qmail@sourceware.org \ --to=agk@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).