From: Brian Gerst <bgerst@didntduck.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
ttabi@interactivesi.com, linux-kernel@vger.kernel.org
Subject: Re: What is the truth about Linux 2.4's RAM limitations?
Date: Tue, 10 Jul 2001 15:35:26 -0400 [thread overview]
Message-ID: <3B4B58FE.642136EB@didntduck.org> (raw)
In-Reply-To: <200107101812.NAA01171@tomcat.admin.navo.hpc.mil> <3B4B4966.996DD91E@didntduck.org> <20010711064355.F32421@weta.f00f.org>
Chris Wedgwood wrote:
>
> On Tue, Jul 10, 2001 at 02:28:54PM -0400, Brian Gerst wrote:
>
> Jesse Pollard wrote:
>
> > If the entire page table were given to a user, then a full cache
> > flush would have to be done on every context switch and system
> > call. That would be very slow, but would allow a full 4G address
> > for the user.
>
> A full cache flush would be needed at every entry into the kernel,
> including hardware interrupts. Very poor for performance.
>
> Why would a cache flush be necessary at all? I assume ia32 caches
> where physically not virtually mapped?
I meant TLB flush, sorry.
--
Brian Gerst
next prev parent reply other threads:[~2001-07-10 19:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 18:12 What is the truth about Linux 2.4's RAM limitations? Jesse Pollard
2001-07-10 18:22 ` Jonathan Lundell
2001-07-10 18:28 ` Brian Gerst
2001-07-10 18:43 ` Chris Wedgwood
2001-07-10 19:35 ` Brian Gerst [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-11 4:31 alad
2001-07-10 21:49 Jesse Pollard
2001-07-10 22:07 ` Jonathan Lundell
2001-07-10 18:38 Jesse Pollard
2001-07-10 19:14 ` Mark H. Wood
2001-07-09 21:29 Jesse Pollard
2001-07-10 17:01 ` Timur Tabi
[not found] <Pine.LNX.4.32.0107091250170.25061-100000@maus.spack.org.suse.lists.linux.kernel>
2001-07-09 21:03 ` Andi Kleen
2001-07-09 20:01 Adam Shand
2001-07-09 21:15 ` Brian Gerst
2001-07-09 21:18 ` Rik van Riel
2001-07-09 22:17 ` Matti Aarnio
2001-07-10 13:49 ` Chris Wedgwood
2001-07-10 17:03 ` Timur Tabi
2001-07-10 17:35 ` Richard B. Johnson
2001-07-10 18:01 ` Timur Tabi
2001-07-10 18:08 ` Jonathan Lundell
2001-07-10 18:45 ` Richard B. Johnson
2001-07-10 19:26 ` Jonathan Lundell
2001-07-10 23:56 ` Jesse Pollard
2001-07-10 20:19 ` Malcolm Beattie
2001-07-10 3:01 ` jlnance
2001-07-10 3:29 ` Michael Bacarella
2001-07-16 8:37 ` Ingo Oeser
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=3B4B58FE.642136EB@didntduck.org \
--to=bgerst@didntduck.org \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
--cc=ttabi@interactivesi.com \
/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