linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@cthulhu.engr.sgi.com>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: Rik van Riel <riel@nl.linux.org>,
	Kanoj Sarcar <kanoj@google.engr.sgi.com>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: Getting big areas of memory, in 2.3.x?
Date: Fri, 10 Dec 1999 10:04:49 -0800 (PST)	[thread overview]
Message-ID: <14417.16577.210091.926383@liveoak.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9912101437330.4472-100000@chiara.csoma.elte.hu>

Ingo Molnar writes:
...
 > this is possible (sans the relocation process which is a special thing
 > anyway), but why would we want to allocate large chunks of contiguous user
 > pages?
...

     To be able to use, for example, 2 or 4 MB pages on x86 to reduce
TLB thrashing (and, if the I/O path understands large pages, the software
overhead to set up large direct or raw I/O requests).

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  reply	other threads:[~1999-12-10 18:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09  1:03 Jeff Garzik
1999-12-09  2:28 ` Alan Cox
1999-12-09  2:45   ` Jeff Garzik
1999-12-09  5:22     ` Oliver Xymoron
1999-12-09 12:25     ` Ingo Molnar
1999-12-09 20:24       ` Jeff Garzik
1999-12-09 20:31         ` Kanoj Sarcar
1999-12-09 20:39           ` Rik van Riel
1999-12-09 20:54             ` Kanoj Sarcar
1999-12-09 23:21               ` Ingo Molnar
1999-12-09 22:27                 ` Kanoj Sarcar
1999-12-09 23:16             ` Ingo Molnar
1999-12-09 23:09               ` Benjamin C.R. LaHaise
1999-12-10  0:44                 ` Ingo Molnar
1999-12-10  0:18                   ` William J. Earl
1999-12-11 19:56                   ` Stephen C. Tweedie
1999-12-10 12:21               ` Rik van Riel
1999-12-10 13:42                 ` Ingo Molnar
1999-12-10 18:04                   ` William J. Earl [this message]
1999-12-09 20:50           ` William J. Earl
1999-12-09 23:15         ` Ingo Molnar
1999-12-09 22:13           ` William J. Earl
1999-12-09 22:26             ` Alan Cox
1999-12-09 23:42               ` William J. Earl
1999-12-09 23:50                 ` Alan Cox
1999-12-10  0:30                   ` William J. Earl
1999-12-10  0:37                     ` Alan Cox
1999-12-10  4:19                   ` Oliver Xymoron
1999-12-10 10:14                   ` Thomas Sailer
1999-12-09 23:24             ` Ingo Molnar
1999-12-09 22:33               ` Jeff Garzik
1999-12-09 23:32               ` Rogier Wolff
1999-12-09 23:44                 ` JF Martinez
1999-12-10  0:52                   ` Ingo Molnar
1999-12-09 23:46                 ` Andi Kleen
1999-12-10 13:52       ` Stephen C. Tweedie

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=14417.16577.210091.926383@liveoak.engr.sgi.com \
    --to=wje@cthulhu.engr.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=riel@nl.linux.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