All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: linux-kernel@vger.kernel.org
Cc: Martin Zwickel <martin.zwickel@technotrend.de>,
	Andrew Morton <akpm@osdl.org>,
	support@nvidia.com
Subject: Re: 2.6.5-rc2-mm2
Date: Wed, 24 Mar 2004 12:35:51 +0100	[thread overview]
Message-ID: <200403241235.51786@WOLK> (raw)
In-Reply-To: <20040324110014.4cdb7597@phoebee>

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

On Wednesday 24 March 2004 11:00, Martin Zwickel wrote:

Hi Martin,

> I'm unable to start my X server with this patch.
> I have the nvidia 5336 module loaded and if I start the X server, the
> machine completely freezes. With 2.6.5-rc2 everything works ok...
> If anyone wants my config, ask me.

apply this patch ontop of 2.6.5-rc2-mm2 tree to get nvidia working again.

nvidia inc: *hint hint* ;)

ciao, Marc

[-- Attachment #2: 4k-reenable.patch --]
[-- Type: text/x-diff, Size: 789 bytes --]

diff -Naurp linux-2.6.5-rc1-mm1/arch/i386/Kconfig linux-2.6.5-rc1-mm1-removed/arch/i386/Kconfig
--- linux-2.6.5-rc1-mm1/arch/i386/Kconfig	2004-03-16 21:28:03.000000000 +0100
+++ linux-2.6.5-rc1-mm1-removed/arch/i386/Kconfig	2004-03-16 21:32:08.000000000 +0100
@@ -1555,7 +1555,14 @@ config MAGIC_SYSRQ
 	default y
 
 config 4KSTACKS
-	def_bool y
+	bool "Use 4Kb for kernel stacks instead of 8Kb"
+	default n
+	help
+	  If you say Y here the kernel will use a 4Kb stacksize for the
+	  kernel stack attached to each process/thread. This facilitates
+	  running more threads on a system and also reduces the pressure
+	  on the VM subsystem for higher order allocations. This option
+	  will also use IRQ stacks to compensate for the reduced stackspace.
 
 config X86_FIND_SMP_CONFIG
 	bool

  parent reply	other threads:[~2004-03-24 11:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24  7:25 2.6.5-rc2-mm2 Andrew Morton
2004-03-24  8:08 ` 2.6.5-rc2-mm2 Piet Delaney
2004-03-24  8:22 ` 2.6.5-rc2-mm2 Marc-Christian Petersen
2004-03-24  8:28   ` 2.6.5-rc2-mm2 Marc-Christian Petersen
2004-03-24 10:00 ` 2.6.5-rc2-mm2 Martin Zwickel
2004-03-24 10:05   ` 2.6.5-rc2-mm2 Andrew Morton
2004-03-24 10:14     ` 2.6.5-rc2-mm2 Martin Zwickel
2004-03-24 11:35   ` Marc-Christian Petersen [this message]
2004-03-24 12:12     ` 2.6.5-rc2-mm2 Geert Uytterhoeven
2004-03-24 14:01 ` 2.6.5-rc2-mm2 Helge Hafting
2004-03-24 14:19   ` 2.6.5-rc2-mm2 Arjan van de Ven
2004-03-24 15:43     ` 2.6.5-rc2-mm2 Mark McPherson
2004-03-28 19:49     ` 2.6.5-rc2-mm2 Helge Hafting
2004-03-24 14:57 ` 2.6.5-rc2-mm2 Alexander Hoogerhuis
2004-03-24 20:16   ` 2.6.5-rc2-mm2 Andrew Morton
2004-03-24 18:54 ` 2.6.5-rc2-mm2 Andreas Happe
2004-03-24 21:06   ` 2.6.5-rc2-mm2 Andrew Morton
2004-03-24 23:46     ` 2.6.5-rc2-mm2 Andreas Happe
2004-03-25 18:41       ` 2.6.5-rc2-mm2 Andreas Happe
2004-03-24 21:32   ` 2.6.5-rc2-mm2 Olaf Hering
2004-03-25 22:26 ` -mm: md-merging-fix causes ICE with gcc 2.95 Adrian Bunk
2004-04-01 13:49 ` 2.6.5-rc2-mm2 Mikael Pettersson
2004-04-01 19:30   ` 2.6.5-rc2-mm2 Andrew Morton
2004-04-01 21:46     ` 2.6.5-rc2-mm2 Mikael Pettersson
  -- strict thread matches above, loose matches on Subject: below --
2004-03-24 23:49 2.6.5-rc2-mm2 Sid Boyce
2004-03-25  1:23 2.6.5-rc2-mm2 Sid Boyce

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=200403241235.51786@WOLK \
    --to=m.c.p@wolk-project.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.zwickel@technotrend.de \
    --cc=support@nvidia.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.