public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW_DM libdm/mm/pool-fast.c
Date: Thu, 20 Oct 2011 14:43:00 -0000 [thread overview]
Message-ID: <20111020144334.2715.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2011-10-20 14:43:33
Modified files:
. : WHATS_NEW_DM
libdm/mm : pool-fast.c
Log message:
Aling structure chunk on default aling size
Since we use 8 bytes by default for the pool allocation,
keep the structure aligned with this size.
(Somehow it was not applied in previous commit.)
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.516&r2=1.517
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/libdm/mm/pool-fast.c.diff?cvsroot=lvm2&r1=1.15&r2=1.16
--- LVM2/WHATS_NEW_DM 2011/10/20 13:39:57 1.516
+++ LVM2/WHATS_NEW_DM 2011/10/20 14:43:33 1.517
@@ -1,7 +1,7 @@
Version 1.02.68 -
==================================
Fix valgrind error reports in free of pool chunks with DEBUG_MEM.
- Aling size of structure chunk for fast pool allocator to 8 bytes.
+ Align size of structure chunk for fast pool allocator to 8 bytes.
Simplify some pointer operations in dm_free_aux() debug code.
Remove unused dbg_malloc.h file from source tree.
Cleanup backtraces for _create_and_load_v4().
--- LVM2/libdm/mm/pool-fast.c 2011/10/20 13:39:57 1.15
+++ LVM2/libdm/mm/pool-fast.c 2011/10/20 14:43:33 1.16
@@ -23,7 +23,7 @@
struct chunk {
char *begin, *end;
struct chunk *prev;
-};
+} __attribute__((aligned(8)));
struct dm_pool {
struct dm_list list;
next reply other threads:[~2011-10-20 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 14:43 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-23 15:38 zkabelac
2011-10-20 13:39 zkabelac
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=20111020144334.2715.qmail@sourceware.org \
--to=zkabelac@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).