linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Andrea Arcangeli <andrea@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rik van Riel <riel@nl.linux.org>,
	linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: [RFC] 2.3.39 zone balancing
Date: Thu, 13 Jan 2000 17:17:32 -0800 (PST)	[thread overview]
Message-ID: <200001140117.RAA86279@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10001140304570.7119-100000@chiara.csoma.elte.hu> from "Ingo Molnar" at Jan 14, 2000 03:13:48 AM

> 
> 
> On Thu, 13 Jan 2000, Linus Torvalds wrote:
> 
> > HOWEVER, I don't think this is going to be a huge issue in most cases. And
> > if people don't need non-DMA memory, then the pages we "swapped" out are
> > going to stay in RAM anyway, so it's not going to hurt us.
> > 
> > Anyway, I obviously do agree that I may well be wrong, and that real life
> > is going to come back and bite us, and we'll end up having to not do it
> > this way. However, I'd prefer trying the "conceptually simple" path first,
> > and only if it turns out that yes, I was completely wrong, do we try to
> > fix it up with magic heuristics etc.
> 
> hm., i think we'll see this with ISA soundcards (still the majority) if
> used as modules. Right now kswapd just gives up too easy and says 'no such
> page', on a box with lots of RAM and all DMA allocated in process VM
> space.
> 
> Anyway, the patch and suggestion of passing in a single zone is i believe
> completely wrong, because it advances mm->swap_address, which unfairly
> selects a given range to be checked for only one zone. So i think it's
> either zone-bitmaps (or equivalent multi-zone logic) or what you
> suggested, to have no zone-awareness in swap_out() for now at all.
> 
> (i believe this is also going to bite us with the IA64 port - kswapd will
> have no information to free pages from the right node, we could solve this
> already with a zone bitmap, or by starting per-zone kswapds. The latter

If you are talking about the discontig memory support, yes, I have thought
about that and arrived at the conclusion that rather than overdesign
right now, we will have to see how things work out on a real machine. 

There's been some arguments against per-zone, or per-node kswapd's, 
so the other alternative is to pass the list of unbalanced zones to
kswapd, which can then scan only the unbalanced ones. This is the 
best solution when there are fairly large number of nodes.

Kanoj

> one looks like overkill to me, but it's conceptually cleaner than bitmaps
> and and does not have a limitation on the number of zones. Might not be a
> highprio issue though.)
> 
> -- mingo
> 

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

  reply	other threads:[~2000-01-14  1:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-12 21:11 Kanoj Sarcar
2000-01-13 13:40 ` Rik van Riel
2000-01-13 17:06   ` Andrea Arcangeli
2000-01-13 17:18   ` Alan Cox
2000-01-13 18:37     ` Rik van Riel
2000-01-13 20:13       ` Andrea Arcangeli
2000-01-13 21:12         ` Rik van Riel
2000-01-13 21:40         ` Kanoj Sarcar
2000-01-14 12:25           ` Jamie Lokier
2000-01-14 13:43             ` Andrea Arcangeli
2000-01-13 18:52   ` Kanoj Sarcar
2000-01-13 19:59     ` Andrea Arcangeli
2000-01-13 21:02       ` Kanoj Sarcar
2000-01-13 21:34         ` Benjamin C.R. LaHaise
2000-01-13 21:48           ` Kanoj Sarcar
2000-01-13 21:42         ` Alan Cox
2000-01-13 21:50           ` Kanoj Sarcar
2000-01-13 21:53             ` Alan Cox
2000-01-13 22:01           ` Linus Torvalds
2000-01-13 22:13             ` Kanoj Sarcar
2000-01-13 22:28               ` Rik van Riel
2000-01-13 22:30               ` Linus Torvalds
2000-01-13 23:53                 ` Ingo Molnar
2000-01-13 23:29                   ` Linus Torvalds
2000-01-14  0:33                     ` Andrea Arcangeli
2000-01-14  0:52                       ` Linus Torvalds
2000-01-14  1:08                         ` Rik van Riel
2000-01-14  2:13                         ` Ingo Molnar
2000-01-14  1:17                           ` Kanoj Sarcar [this message]
2000-01-14  2:36                             ` Ingo Molnar
2000-01-14 20:33                               ` Peter Rival
2000-01-14  1:13                       ` Kanoj Sarcar
2000-01-14  2:27                         ` Ingo Molnar
2000-01-14  2:46                         ` Ingo Molnar
2000-01-14  6:22                           ` Kanoj Sarcar
2000-01-15  2:03                     ` Reworked 2.3.39 zone balancing - v1 Kanoj Sarcar
2000-01-14  0:28                 ` [RFC] 2.3.39 zone balancing Andrea Arcangeli
2000-01-13 17:12 ` Andrea Arcangeli
2000-01-13 18:30   ` Kanoj Sarcar
2000-01-13 19:22     ` Andrea Arcangeli

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=200001140117.RAA86279@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --cc=riel@nl.linux.org \
    --cc=torvalds@transmeta.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