linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Philipp Rumpf <prumpf@uzix.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: sys_exit() and zap_page_range()
Date: Sun, 09 Jul 2000 23:54:54 +0000	[thread overview]
Message-ID: <396910CE.64A79820@uow.edu.au> (raw)
In-Reply-To: <20000709103011.A3469@fruits.uzix.org>

Philipp Rumpf wrote:
> 

Hi, Philipp.

> Here's a simple way:

Already done it :)  It's apparent that not _all_ callers of z_p_r need
this treatment, so I've added an extra 'do_reschedule' flag.  I've also
moved the TLB flushing into this function.

It strikes me that the TLB flush race can be avoided by simply deferring
the actual free_page until _after_ the flush.  So
free_page_and_swap_cache simply appends them to a passed-in list rather
than returning them to the buddy allocator.  zap_page_range can then
free the pages after the flush.

What am I missing???

 
> [PAGE_SIZE*4 is low, I suspect.]

zap_page_range zaps 1000 pages per millisecond, so I'm doing 1000 at a
time.

> For a clean solution, what I would love zap_page_range to look like is:

I'll look at it, but I'm not an MM guy....
--
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.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2000-07-09 23:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 14:43 Andrew Morton
2000-07-07 16:42 ` Manfred Spraul
2000-07-09 17:30 ` Philipp Rumpf
2000-07-09 17:42   ` Arjan van de Ven
2000-07-09 23:54   ` Andrew Morton [this message]
2000-07-10  9:53     ` Philipp Rumpf
2000-07-10 15:36       ` Andrew Morton
2000-07-10 17:34         ` Philipp Rumpf
2000-07-11  8:39 ` Stephen C. Tweedie
2000-07-11 11:24   ` Andrew Morton
2000-07-11 13:35     ` Stephen C. Tweedie
2000-07-11 15:23       ` Richard Guenther

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=396910CE.64A79820@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-mm@kvack.org \
    --cc=prumpf@uzix.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