From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: should all THREAD_SIZE macros be defined in thread_info.h headers?
Date: Wed, 12 Dec 2007 13:45:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0712121342020.28488@localhost.localdomain> (raw)
just asking, given that:
include/asm-x86/page_64.h:#define THREAD_SIZE (PAGE_SIZE << THREAD_ORDER)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE (8192)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE PAGE_SIZE
include/asm-cris/processor.h:#define THREAD_SIZE PAGE_SIZE
include/asm-m32r/processor.h:#define THREAD_SIZE (2*PAGE_SIZE)
include/asm-m68k/page.h:#define THREAD_SIZE (8192)
all other arches seem to define that in their respective
thread_info.h headers.
rday
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
reply other threads:[~2007-12-12 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.0.9999.0712121342020.28488@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-kernel@vger.kernel.org \
/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®