From: Kumar Gala <kumar.gala@freescale.com>
To: "Dan Malek" <dan@embeddededge.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] ppc32: fix CONFIG_TASK_SIZE handling on 44x
Date: Wed, 18 May 2005 11:19:15 -0500 [thread overview]
Message-ID: <96c735b4d1269864b56c84c72a8a4ac3@freescale.com> (raw)
In-Reply-To: <55497ec3de50301c9f568be24ed3edac@embeddededge.com>
On May 18, 2005, at 9:14 AM, Dan Malek wrote:
>
>
> On May 18, 2005, at 6:21 AM, Eugene Surovegin wrote:
>
> > This patch fixed CONFIG_TASK_SIZE handling on 44x.
>
> Paul suggested to me and I've been contemplating changing
> the page table management on PowerPC to something similar
> to other platforms.=A0 At first, I was only going to do this on 8xx,
> but I think I'll do it for PowerPC in general so all boards can
> take advantage if they choose to do so.
>
> Other ports populate the user page tables with the kernel pmd
> entries upon kernel faults, then we don't have to distinguish
> among page tables during the TLB exceptions.=A0 I'm hoping we
> can populate the init page table entries at boot time, and then
> everyone will inherit them, eliminating all faults unless the kernel
> vmalloc space grows to need a new pmd entry.
I'm a bit concerned about this in the future. On Book-E parts we may=20
end up actually utilizing the address space bit to provide a true 4G/4G=20=
split. I understand the current pain in doing this today. I just want=20=
you to be aware of what the future might bring.
> This would be a generic solution to selecting task size, among
> other advanced memory mapping options.
>
> I'll keep you posted.
While we wait on this I think getting Eugene's patch is worth while.
- kumar
next prev parent reply other threads:[~2005-05-18 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 10:21 [PATCH] ppc32: fix CONFIG_TASK_SIZE handling on 44x Eugene Surovegin
2005-05-18 14:14 ` Dan Malek
2005-05-18 16:19 ` Kumar Gala [this message]
2005-05-18 16:34 ` Matt Porter
2005-05-18 16:48 ` Dan Malek
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=96c735b4d1269864b56c84c72a8a4ac3@freescale.com \
--to=kumar.gala@freescale.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.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).