From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>, Dan Malek <dan@embeddededge.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: CONFIG_PIN_TLB and telnet problems
Date: Tue, 4 Jun 2002 14:37:08 +0200 [thread overview]
Message-ID: <20020604123708.13854@smtp.adsl.oleane.com> (raw)
In-Reply-To: <20020604122046.29082@mailhost.mipsys.com>
>
>To add to these comments, I can reproduce the problem as well on a
>unix socket shared either between two processes, or read & written
>by a single process.
>
>After doing various tests, the problem appears rarely and randomly
>with half the RAM mapped with fixed TLBs, and very reproduceably
>with all the RAM mapped this way. So it seems that reducing the
>kernel pressure on TLBs, thus allowing userland TLBs to live much
>longer, exhibit the problem.
>
>I tried adding a call to _tlbia (not the instruction but our tlbwe
>based implementation) in set_context to make sure I only ever have
>one userland context loaded in the TLB and this appear to kill the
>problem (I'm currently running 2 offending test programs simultaneously
>on the box and none failed yet after a few Gb transferred).
Hrm... I added isync/sync (actually, the sync is probably too much)
to set_context() in head_4xx.S in order to invalidate the shadow TLBs
and it seems to work ! I'll test a few hours and let you know.
Ben.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-06-04 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 7:15 CONFIG_PIN_TLB and telnet problems David Gibson
2002-05-31 7:27 ` David Gibson
2002-06-04 0:54 ` Dan Malek
2002-06-04 1:26 ` Paul Mackerras
2002-06-04 12:20 ` benh
2002-06-04 12:37 ` Benjamin Herrenschmidt [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=20020604123708.13854@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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.