Question on thread_info

• To: [email protected]
• Subject: Question on thread_info
• From: Purshotam Roy <[email protected]>
• Date: Fri, 15 Jul 2005 06:07:11 +0530
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=kYoH4X22sFRf+3QyHL9ZCe8TDHaRxMN4bOCPz+TIru6mnR6HiQp4qRdbsg5KQRXZ50KllvvBHOvMl9JW5ZvawKU9YtQ/fxEV0QCbV8ZFInAimEn+m5r/wZbz074+iNahrRg/WBJ7YgEgN6A3bpaQQRV1Stoel/xC3Usda12FaNo=
• Reply-to: Purshotam Roy <[email protected]>
• Sender: [email protected]

Hello,
	Could anybody provide any information as to why thread_info is kept
at the top of the stack. Also, does it mean that when thread_info is
kept it will be kept at the bottom of the heap itself also.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: [rfc patch 2/2] direct-io: remove address alignment check
• Next by Date: Re: Why is 2.6.12.2 less stable on my laptop than 2.6.10?
• Previous by thread: [patch 1/2] block/cpqarray: Audit return code of create_proc_*
• Next by thread: interrupt hooking in kernel 2.6
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]