From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Adam 'WeirdArms' Wiggins <awiggins@cse.unsw.EDU.AU>
Cc: linux-mm@kvack.org
Subject: Re: exit_mmap()
Date: Sun, 14 Jan 2001 19:15:00 +0000 (GMT) [thread overview]
Message-ID: <200101141915.f0EJF0508827@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.OSF.4.21.0101150424360.24789-100000@paulaner.disy.cse.unsw.EDU.AU> from "Adam 'WeirdArms' Wiggins" at Jan 15, 2001 04:55:24 AM
(About 2.4 kernels)
Adam 'WeirdArms' Wiggins writes:
> The function exit_mmap() in linux/mm/mmap.c does something that I can't
> figure. The function as far as I can tell loops on each vm_area_struct of
> the mm_struct to tear them down. What I don't understand is that while
> doing this if calls flush_cache_range() on the range covered by the
> vm_area_struct. exit_mmap() is called by exec_mmap() in linux/fs/exec.c
> (which calls flush_cache_mm() before exit_mmap() already) and by
> mmput() in linux/kernel/fork.c
>
> Why does exit_mmap() not just call flush_cache_mm() before the while
> loop?
I've CC:'d this to the linux-mm list, and taken the linux-arm-kernel off
the CC: list.
People on linux-mm: please note that neither Adam nor myself are subscribed
to linux-mm.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King linux@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/ / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
--
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:[~2001-01-14 19:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.OSF.4.21.0101150424360.24789-100000@paulaner.disy.cse.unsw.EDU.AU>]
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=200101141915.f0EJF0508827@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=awiggins@cse.unsw.EDU.AU \
--cc=linux-mm@kvack.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