From: Dan Malek <dan@embeddededge•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH] ppc32: fix CONFIG_TASK_SIZE handling on 44x
Date: Wed, 18 May 2005 12:48:57 -0400 [thread overview]
Message-ID: <e8a895753d8d591cb5ca167c3a50000e@embeddededge.com> (raw)
In-Reply-To: <96c735b4d1269864b56c84c72a8a4ac3@freescale.com>
On May 18, 2005, at 12:19 PM, Kumar Gala wrote:
> I'm a bit concerned about this in the future. On Book-E parts we may
> end up actually utilizing the address space bit to provide a true
> 4G/4G split.
I've contemplated the 4G/4G split and we have discussed this for years.
This is why I kept the separate kernel/user page table lookup in the TLB
miss handlers.
This was always lost to the Linux "efficiency" argument due to the
mapping
operations required for accessing user space from the kernel. I don't
remember Book E inventing alternate address space options as m68k
does, and without them it will be lots of kernel modifications to
support
this. I suspect most of them will be under the "...to_from_user ..."
functions
and macros, but there are other places in the kernel where the
mapping is assumed.
> I understand the current pain in doing this today. I just want you
> to be aware of what the future might bring.
As I said, the changes aren't required to be implemented by anyone,
it all depends how you choose to write the tlb management functions
for a particular processor. The infrastructure will be there to choose
either method. Until we actually have totally separate kernel and
user VM spaces, you may as well take advantage of the performance
improvement.
> While we wait on this I think getting Eugene's patch is worth while.
That's fine, it was just an opportunity for me to post the message.
Thanks.
-- Dan
prev parent reply other threads:[~2005-05-18 16:48 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
2005-05-18 16:34 ` Matt Porter
2005-05-18 16:48 ` Dan Malek [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=e8a895753d8d591cb5ca167c3a50000e@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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