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/metadata lv_manip.c pv_map.h
Date: Thu, 25 Mar 2010 02:40:00 -0000	[thread overview]
Message-ID: <20100325024009.6756.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk@sourceware.org	2010-03-25 02:40:09

Modified files:
	lib/metadata   : lv_manip.c pv_map.h 

Log message:
	improve a few comments in last check-in

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/lv_manip.c.diff?cvsroot=lvm2&r1=1.213&r2=1.214
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/pv_map.h.diff?cvsroot=lvm2&r1=1.11&r2=1.12

--- LVM2/lib/metadata/lv_manip.c	2010/03/25 02:31:49	1.213
+++ LVM2/lib/metadata/lv_manip.c	2010/03/25 02:40:09	1.214
@@ -929,7 +929,7 @@
 		return 1;
 
 	/*
-	 * Only used for cling and contiguous policies so its safe to say all
+	 * Only used for cling and contiguous policies so it's safe to say all
 	 * the available space is used.
 	 */
 	pvmatch->areas[s].pva = pvmatch->pva;
--- LVM2/lib/metadata/pv_map.h	2010/03/25 02:31:49	1.11
+++ LVM2/lib/metadata/pv_map.h	2010/03/25 02:40:09	1.12
@@ -39,7 +39,9 @@
  * an allocation attempt, track the maximum number of extents that may
  * need to be used as a particular parallel area.  Several of these
  * structs may reference the same pv_area, but 'used' may differ between
- * them.
+ * them.  The sum of all the 'used' variables referring to the same
+ * pv_area may not exceed that area's count, so we cannot allocate the
+ * same extents twice.
  */
 struct pv_area_used {
 	struct pv_area *pva;


                 reply	other threads:[~2010-03-25  2:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100325024009.6756.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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).