mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <christoph@lameter.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, axboe@suse.de, alexn@dsv.su.se,
	lnxluv@yahoo.com
Subject: Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update]
Date: Tue, 10 May 2005 15:01:13 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0505101457530.23713@graphe.net> (raw)
In-Reply-To: <20050510214918.GQ25612@wotan.suse.de>

On Tue, 10 May 2005, Andi Kleen wrote:

> > +  . = ALIGN(32);
>
> This should be . = ALIGN(CONFIG_X86_L1_CACHE_BYTES)
>
> It was wrong on i386 already btw, which needs the same.

i386 always specifies the numbers and does not use symbolic constants.
We better leave that as it is.

> > +  /* Rarely changed data like cpu maps */
> > +  . = ALIGN(4096);
>
> Does it really need an 4096 byte alignment? That seems like
> a waste of memory. Cache line alignment should be enough.

Ok.

Index: linux-2.6.11/arch/i386/kernel/vmlinux.lds.S
===================================================================
--- linux-2.6.11.orig/arch/i386/kernel/vmlinux.lds.S	2005-05-10 13:35:25.000000000 -0700
+++ linux-2.6.11/arch/i386/kernel/vmlinux.lds.S	2005-05-10 13:59:18.000000000 -0700
@@ -58,7 +58,7 @@ SECTIONS
   }

   /* rarely changed data like cpu maps */
-  . = ALIGN(4096);
+  . = ALIGN(32);
   .data.mostly_readonly : AT(ADDR(.data.mostly_readonly) - LOAD_OFFSET) {
 	*(.data.mostly_readonly)
   }
Index: linux-2.6.11/arch/x86_64/kernel/vmlinux.lds.S
===================================================================
--- linux-2.6.11.orig/arch/x86_64/kernel/vmlinux.lds.S	2005-05-10 13:35:24.000000000 -0700
+++ linux-2.6.11/arch/x86_64/kernel/vmlinux.lds.S	2005-05-10 14:02:06.000000000 -0700
@@ -42,6 +42,13 @@ SECTIONS
 	CONSTRUCTORS
 	}

+  . = ALIGN(CONFIG_X86_L1_CACHE_BYTES);
+  .data.cacheline_aligned : { (.data.cacheline_aligned) }
+
+  /* Rarely changed data like cpu maps */
+  . = ALIGN(CONFIG_X86_L1_CACHE_BYTES);
+  .data.mostly_readonly : { *(.data.mostly_readonly) }
+
   _edata = .;			/* End of data section */

   __bss_start = .;		/* BSS */

  reply	other threads:[~2005-05-10 22:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 20:39 [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 Rafael J. Wysocki
2005-05-09 20:52 ` Andi Kleen
2005-05-10  6:18   ` Jens Axboe
2005-05-10  8:28     ` Alexander Nyberg
2005-05-10  9:02       ` Jens Axboe
2005-05-10 10:55     ` Andi Kleen
2005-05-09 21:54 ` Andrew Morton
2005-05-10 11:49   ` Rafael J. Wysocki
2005-05-10 12:43   ` [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update] Rafael J. Wysocki
2005-05-10 18:22     ` Andrew Morton
2005-05-10 21:11       ` Andi Kleen
2005-05-10 21:44         ` Christoph Lameter
2005-05-10 21:49           ` Andi Kleen
2005-05-10 22:01             ` Christoph Lameter [this message]
2005-05-10 22:15               ` Andi Kleen

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=Pine.LNX.4.58.0505101457530.23713@graphe.net \
    --to=christoph@lameter.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnxluv@yahoo.com \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®