All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: "David S. Miller" <davem@redhat.com>
Cc: anton@samba.org, wli@holomorphy.com, haveblue@us.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [lart] /bin/ps output
Date: Sat, 12 Oct 2002 13:15:01 -0700	[thread overview]
Message-ID: <20021012131501.C25740@twiddle.net> (raw)
In-Reply-To: <20021011.235329.116353173.davem@redhat.com>; from davem@redhat.com on Fri, Oct 11, 2002 at 11:53:29PM -0700

On Fri, Oct 11, 2002 at 11:53:29PM -0700, David S. Miller wrote:
> In fact, thinking about this some more, we should make the ".per_cpu"
> bits emit a table entry instead of some dummy object which takes up
> space.  The table entry would be in the special .per_cpu
> section still but be just a size value.

That's more complicated.  Using the linker to help out with
layout is definitely helpful.  If you want to omit the per-cpu
area from the kernel image, then arrange for it to be .bss.


r~

  reply	other threads:[~2002-10-12 20:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12  3:36 [lart] /bin/ps output Dave Hansen
2002-10-12  3:38 ` David S. Miller
2002-10-12  3:55   ` Rik van Riel
2002-10-12 11:49     ` Alan Cox
2002-10-12  3:43 ` William Lee Irwin III
2002-10-12  3:51 ` Anton Blanchard
2002-10-12  3:59   ` William Lee Irwin III
2002-10-12  4:09     ` Anton Blanchard
2002-10-12  6:53       ` David S. Miller
2002-10-12 20:15         ` Richard Henderson [this message]
2002-10-13  6:27           ` David S. Miller
2002-10-13  6:42             ` Anton Blanchard
2002-10-13 18:25             ` Richard Henderson
2002-10-13 19:25       ` Andrew Morton
2002-10-19 12:22         ` Anton Blanchard
2002-11-16  9:24 ` William Lee Irwin III
2002-11-17  0:11   ` Alan Cox
2002-11-16 23:52     ` Chris Wedgwood
2002-11-17  0:11     ` William Lee Irwin III

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=20021012131501.C25740@twiddle.net \
    --to=rth@twiddle.net \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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.