public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge•com>
To: Eugene Surovegin <ebs@ebshome•net>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH] ppc32: fix CONFIG_TASK_SIZE handling on 44x
Date: Wed, 18 May 2005 10:14:46 -0400	[thread overview]
Message-ID: <55497ec3de50301c9f568be24ed3edac@embeddededge.com> (raw)
In-Reply-To: <20050518102103.GB32493@gate.ebshome.net>


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.  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.  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.

This would be a generic solution to selecting task size, among
other advanced memory mapping options.

I'll keep you posted.

Thanks.


	-- Dan

  reply	other threads:[~2005-05-18 14:14 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 [this message]
2005-05-18 16:19   ` Kumar Gala
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=55497ec3de50301c9f568be24ed3edac@embeddededge.com \
    --to=dan@embeddededge$(echo .)com \
    --cc=ebs@ebshome$(echo .)net \
    --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