From: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Arnaldo de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: pahole BRAIN FART ALERT on F12
Date: Mon, 23 Nov 2009 17:17:03 -0500 [thread overview]
Message-ID: <20091123221703.GA10860@redhat.com> (raw)
Hi,
I just found out about pahole today. I'm looking to audit lvm2's data
structures and pahole is perfect for helping me do so.
Unfortunately, when I run pahole against lvm2 I'm getting many BRAIN
FART ALERTs on F12 x86_64 (dwarves-1.7-5.x86_64). I had a look at your
OLS 2007 "7 dwarves" paper and figured I'd try your minimalist
swiss_cheese example, this is what I get:
$ pahole swiss_cheese
struct cheese {
char name[17]; /* 0 17 */
short int age; /* 0 2 */
char type; /* 0 1 */
int calories; /* 0 4 */
short int price; /* 0 2 */
int barcode[4]; /* 0 16 */
/* size: 48, cachelines: 1, members: 6 */
/* padding: 32 */
/* last cacheline: 48 bytes */
/* BRAIN FART ALERT! 48 != 17 + 0(holes), diff = 31 */
};
When I compare the above to the output listed in your paper it is clear
pahole is pretty unhappy on F12. If I do the same on F11 (x86_64) all
works fine.
Should I open a fedora (F12) bug?
Mike
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-11-23 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 22:17 Mike Snitzer [this message]
[not found] ` <20091123221703.GA10860-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-23 22:49 ` pahole BRAIN FART ALERT on F12 Arnaldo de Melo
[not found] ` <20091123224921.GA9654-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2009-11-23 22:56 ` Mike Snitzer
[not found] ` <20091123225615.GD10860-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-24 0:10 ` Arnaldo de Melo
[not found] ` <20091124001047.GF15547-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2009-11-24 13:28 ` Mike Snitzer
[not found] ` <20091124132831.GA31662-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-11-24 14:52 ` Arnaldo de Melo
[not found] ` <20091124145212.GC9654-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2009-11-24 15:18 ` Mike Snitzer
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=20091123221703.GA10860@redhat.com \
--to=snitzer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 NNTP newsgroup(s).