From: Dan Malek <dan@netx4.com>
To: Peter Allworth <linsol@zeta.org.au>
Cc: Jesper Skov <jskov@redhat.com>,
linuxppc-embedded@lists.linuxppc.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: more Re: Low memory problems in 8xx Linux
Date: Wed, 09 Feb 2000 00:52:13 -0500 [thread overview]
Message-ID: <38A1008D.BB560C55@netx4.com> (raw)
In-Reply-To: 38A0BED6.AD2E336C@zeta.org.au
Just a note to let you guys know you are getting just a little
carried away here.....
You are placing things in the TLB specific handler that are
supposed to be handled generically in places like arch/ppc/mm/fault.c.
Yes, it may be a little bit of a speed improvement, but you
are placing code in the TLB miss handler that logically should
be executed as part of the TLB Error handler. In some cases,
it is appropriate to store something in the TLB that will cause
a subsequent fault into the TLB Error handler (i.e. a pte that
doesn't look valid). If you continue down this path, you will
end up exceeding the space allocated for the trap handler, and
simply re-implement code found elsewhere.
While some of the updates are genuine bugs that should be corrected,
some of the other stuff isn't proper, so don't be surprised when
it doesn't show up in the real kernel sources.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-09 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-31 15:02 Low memory problems in 8xx Linux Marcus Sundberg
2000-02-01 2:51 ` Peter Allworth
2000-02-01 18:08 ` Marcus Sundberg
2000-02-01 19:47 ` Dan Malek
2000-02-01 23:30 ` Peter Allworth
2000-02-01 23:59 ` Dan Malek
2000-02-01 23:54 ` duncanp
2000-02-02 0:25 ` Peter Allworth
2000-02-08 10:01 ` Jesper Skov
2000-02-09 0:00 ` Peter Allworth
2000-02-09 8:43 ` Jesper Skov
2000-02-09 23:26 ` Peter Allworth
2000-02-09 1:11 ` more " Peter Allworth
2000-02-09 5:52 ` Dan Malek [this message]
2000-02-09 8:40 ` Jesper Skov
2000-03-22 15:43 ` Residual data Claude Robitaille
2000-03-23 10:36 ` Gabriel Paubert
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=38A1008D.BB560C55@netx4.com \
--to=dan@netx4.com \
--cc=jskov@redhat.com \
--cc=linsol@zeta.org.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.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).