From: Dan Malek <dan@embeddededge.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: LMbench results for large page patch
Date: Thu, 06 Jun 2002 04:14:46 -0400 [thread overview]
Message-ID: <3CFF19F6.50105@embeddededge.com> (raw)
In-Reply-To: 20020606075732.GY2630@zax
David Gibson wrote:
> So are you ok with the notion of merging the large page stuff and
> abolishing CONFIG_PIN_TLB, once I've made iopa() and mapin_ram() less
> ugly than they are in that first cut?
I guess. When I add my stuff I'll further clean it up :-) There still
may be some latency sensitive applications that would benefit from some
pinned TLBs, but if we ever find them I guess we can fetch anything useful
from archives. I'm glad this exercise actually found the couple of tlb
management bugs. So much to do, so little time.........
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-06-06 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 7:08 LMbench results for large page patch David Gibson
2002-06-06 4:29 ` David Gibson
2002-06-06 7:30 ` Dan Malek
2002-06-06 7:57 ` David Gibson
2002-06-06 8:14 ` 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=3CFF19F6.50105@embeddededge.com \
--to=dan@embeddededge.com \
--cc=david@gibson.dropbear.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.