linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "William J. Earl" <wje@cthulhu.engr.sgi.com>
Cc: alan@lxorguk.ukuu.org.uk, mingo@chiara.csoma.elte.hu,
	jgarzik@mandrakesoft.com, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: Getting big areas of memory, in 2.3.x?
Date: Thu, 9 Dec 1999 23:50:04 +0000 (GMT)	[thread overview]
Message-ID: <E11wDK1-0002nT-00@the-village.bc.nu> (raw)
In-Reply-To: <14416.15954.354222.915088@liveoak.engr.sgi.com> from "William J. Earl" at Dec 9, 99 03:42:10 pm

> For example, large pages for programs with large code or data footprints
> can dramatically reduce TLB misses.  If the I/O system learns to do direct

Yep. One thing Irix always seemed to be rather neat about was page size
dependant on ram size of box.

> I/O, the overhead of setting up large I/O operations, whether for disk I/O
> or for OpenGL operations such as writing a large image to the screen
> (via DMA), is much reduced when the I/O is done from large pages.

PC's have the AGP GART. That provides an MMU for the graphics card in effect.

> for higher-bandwidth targets, such as a graphics controller or a 
> HDTV camera.

I don't know of any capture cards that don't do scatter gather. Most of them
do scatter gather with skipping and byte alignment so you can DMA around
other windows.

This is the main point. There are so so few devices that actually _have_ to
have lots of linear memory it is questionable that it is worth paying the
price to allow modules to allocate that way

--
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-09 23:50 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
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 [this message]
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=E11wDK1-0002nT-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=wje@cthulhu.engr.sgi.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