From: Takeharu KATO <tkato@cs.fujitsu.co.jp>
To: paulus@samba.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Task tsruct relevant question
Date: Fri, 18 Apr 2003 11:44:43 +0900 [thread overview]
Message-ID: <3E9F669B.7A2B1C72@cs.fujitsu.co.jp> (raw)
In-Reply-To: 16031.22226.295030.685058@nanango.paulus.ozlabs.org
Paul Mackerras wrote:
>
> Takeharu KATO writes:
>
> > I have a queestion about task_struct relevant issue.
> > As far as I know, task_structs in kernel 2.5.X are placed in
> > slab cache. But they are placed on kernel stack on linux-2.4.67
> > for PPC4xx.
Sorry. I made typo.
I wanted to say task_struct is not separated from kernel stack
in linux-2.5.67 for PPC4xx support.
Does anyone have plan to separate task_struct from kernel stacks
for PPC4xx port?
--
Takeharu KATO
Fujitsu Limited
Email:tkato@cs.fujitsu.co.jp (ext. 7112-4621)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-04-18 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 0:17 Task tsruct relevant question Takeharu KATO
2003-04-18 1:37 ` Paul Mackerras
2003-04-18 2:44 ` Takeharu KATO [this message]
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=3E9F669B.7A2B1C72@cs.fujitsu.co.jp \
--to=tkato@cs.fujitsu.co.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).