From: Stephan von Krawczynski <skraw@ithnet.com>
To: Timothy Miller <miller@techsource.com>
Cc: alan@lxorguk.ukuu.org.uk, marcelo.tosatti@cyclades.com.br,
neilb@cse.unsw.edu.au, linux-kernel@vger.kernel.org
Subject: Re: experiences beyond 4 GB RAM with 2.4.22
Date: Tue, 16 Sep 2003 18:17:08 +0200 [thread overview]
Message-ID: <20030916181708.5b63ed00.skraw@ithnet.com> (raw)
In-Reply-To: <3F6730F6.8040508@techsource.com>
On Tue, 16 Sep 2003 11:49:10 -0400
Timothy Miller <miller@techsource.com> wrote:
> Alan Cox wrote:
> > The kernel has no idea what you will do with given ram. It does try to
> > make some guesses but you are basically trying to paper over hardware
> > limits.
>
>
> Maybe not what you WILL DO, but what you HAVE DONE. Those tasks which
> have done the most DMA-requiring I/O could get preference for low
> memory. No?
>
> Yeah, I know.. show you the code. :)
That really sounds complex and therefore I would not try that in first place.
And it does not sound like a solution to my special problem of few tasks
operating on a lot of data (a lot more than fits to physical mem). For this
type of situation it would be really intelligent not to give away non-dma-able
memory. How can the kernel do that?
At least it knows that there are I/O devices that cannot cope with the mem it
is presenting. This sounds in fact simple.
The problem is: what _can_ be done with this type of mem at all?
It does not even help a lot if there are other devices that can handle it,
because you still must face the fact of a simple file-copy from such a capable
device to one that is not.
No wonder that the gurus did not have any good idea yet ;-)
Regards,
Stephan
next prev parent reply other threads:[~2003-09-16 16:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 9:01 experiences beyond 4 GB RAM with 2.4.22 Stephan von Krawczynski
2003-09-09 12:25 ` Andrea Arcangeli
2003-09-12 2:46 ` Neil Brown
2003-09-12 6:54 ` Stephan von Krawczynski
2003-09-12 7:11 ` Jens Axboe
2003-09-12 7:53 ` Mike Fedyk
2003-09-15 22:01 ` Marcelo Tosatti
2003-09-16 8:21 ` Stephan von Krawczynski
2003-09-16 12:05 ` Stephan von Krawczynski
2003-09-16 13:11 ` Marcelo Tosatti
2003-09-16 13:36 ` Stephan von Krawczynski
2003-09-16 13:55 ` Richard B. Johnson
2003-09-16 14:13 ` Stephan von Krawczynski
2003-09-16 14:33 ` Marcelo Tosatti
2003-09-16 14:36 ` Stephan von Krawczynski
2003-09-16 14:36 ` Alan Cox
2003-09-16 15:20 ` Stephan von Krawczynski
2003-09-16 15:29 ` Alan Cox
2003-09-16 15:49 ` Timothy Miller
2003-09-16 16:17 ` Stephan von Krawczynski [this message]
2003-09-16 19:58 ` Olivier Galibert
2003-09-17 15:10 ` Alan Cox
2003-09-17 19:19 ` Jens Axboe
2003-09-17 19:30 ` Marcelo Tosatti
2003-09-17 22:18 ` Stephan von Krawczynski
2003-09-18 7:08 ` Jens Axboe
2003-09-18 7:12 ` Jens Axboe
2003-09-18 11:22 ` Stephan von Krawczynski
2003-09-18 15:05 ` William Lee Irwin III
2003-09-16 17:10 ` Pavel Machek
2003-09-16 19:53 ` Olivier Galibert
2003-09-16 20:04 ` Pavel Machek
2003-09-16 21:16 ` Marcelo Tosatti
2003-09-16 21:23 ` Olivier Galibert
2003-09-17 11:14 ` Stephan von Krawczynski
2003-09-17 13:08 ` Olivier Galibert
2003-09-18 9:58 ` Olivier Galibert
2003-09-18 10:13 ` Stephan von Krawczynski
2003-09-18 11:22 ` Olivier Galibert
2003-09-17 6:41 ` Rogier Wolff
2003-09-17 10:26 ` Jens Axboe
2003-09-17 10:42 ` Rogier Wolff
2003-09-17 10:53 ` Jens Axboe
2003-09-17 19:19 ` Pavel Machek
2003-09-18 11:39 ` Rogier Wolff
2003-09-18 12:13 ` Rogier Wolff
2003-09-16 15:22 ` Timothy Miller
2003-09-16 15:29 ` Martin J. Bligh
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=20030916181708.5b63ed00.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=miller@techsource.com \
--cc=neilb@cse.unsw.edu.au \
/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.