From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: penberg@cs.helsinki.fi, christoph@lameter.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
manfred@colorfullife.com
Subject: Re: [RFT/PATCH] slab: consolidate allocation paths
Date: Sat, 4 Feb 2006 20:36:17 -0800 [thread overview]
Message-ID: <20060204203617.f773606a.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602041941570.9005@schroedinger.engr.sgi.com>
Christoph wrote:
> Hmmm... Maybe its worth a retry with gcc 3.4 and 4.X? Note that the
> size increase may be much less on i386. The .o file includes descriptive
> material too...
Yes, the other gcc's will no doubt have a different amount of increase.
Yes, i386 text sizes seem to run half the size of ia64.
No, I said "text" size, not file size. Meaning with the size command.
That same 776 byte size difference in text size showed up in the final
vmlinux, which I just verified.
This is not a 'big problem.' It's just a curiosity, for which an
explanation might provide interesting insight to what this patch is
doing.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: penberg@cs.helsinki.fi, christoph@lameter.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
manfred@colorfullife.com
Subject: Re: [RFT/PATCH] slab: consolidate allocation paths
Date: Sat, 4 Feb 2006 20:36:17 -0800 [thread overview]
Message-ID: <20060204203617.f773606a.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602041941570.9005@schroedinger.engr.sgi.com>
Christoph wrote:
> Hmmm... Maybe its worth a retry with gcc 3.4 and 4.X? Note that the
> size increase may be much less on i386. The .o file includes descriptive
> material too...
Yes, the other gcc's will no doubt have a different amount of increase.
Yes, i386 text sizes seem to run half the size of ia64.
No, I said "text" size, not file size. Meaning with the size command.
That same 776 byte size difference in text size showed up in the final
vmlinux, which I just verified.
This is not a 'big problem.' It's just a curiosity, for which an
explanation might provide interesting insight to what this patch is
doing.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-02-05 4:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 13:33 [RFT/PATCH] slab: consolidate allocation paths Pekka Enberg
2006-02-04 13:33 ` Pekka Enberg
2006-02-04 15:11 ` Christoph Lameter
2006-02-04 15:11 ` Christoph Lameter
2006-02-04 16:26 ` Pekka Enberg
2006-02-04 16:26 ` Pekka Enberg
2006-02-04 16:32 ` Pekka Enberg
2006-02-04 16:32 ` Pekka Enberg
2006-02-05 2:00 ` Paul Jackson
2006-02-05 2:00 ` Paul Jackson
2006-02-05 3:44 ` Christoph Lameter
2006-02-05 3:44 ` Christoph Lameter
2006-02-05 4:36 ` Paul Jackson [this message]
2006-02-05 4:36 ` Paul Jackson
2006-02-05 8:41 ` Pekka Enberg
2006-02-05 8:41 ` Pekka Enberg
2006-02-05 9:18 ` Pekka Enberg
2006-02-05 9:18 ` Pekka Enberg
2006-02-05 12:29 ` Pekka Enberg
2006-02-05 12:29 ` Pekka Enberg
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=20060204203617.f773606a.pj@sgi.com \
--to=pj@sgi.com \
--cc=christoph@lameter.com \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.