From: Brian Gerst <bgerst@didntduck.org>
To: Venu Vadapalli <bvadapal@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vmalloc/vfree
Date: Tue, 10 Sep 2002 09:33:37 -0400 [thread overview]
Message-ID: <3D7DF4B1.6010300@didntduck.org> (raw)
In-Reply-To: 3D81FB0C@zathras
Venu Vadapalli wrote:
> Looking at vmalloc implementation, it fills the page table mappings (pgd and
> pmd) of only init_mm. When other tasks access these pages their mappings are
> updated on demand by the page fault handler, right? Vfree, also, updates the
> entries of just init_mm and, of course, flushes the cache and the tlb. But
> what about other tasks that have acquired mappings to these pages?
>
> -Venu
The pagetables for the kernel space are shared between all processes,
except for the top level which is why the page fault handler exists.
The actual pages that make up the shared pagetables never change once
allocated which is the reason we can be lazy about updating the top
level table of each task.
--
Brian Gerst
prev parent reply other threads:[~2002-09-10 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 1:12 vmalloc/vfree Venu Vadapalli
2002-09-10 13:33 ` Brian Gerst [this message]
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=3D7DF4B1.6010300@didntduck.org \
--to=bgerst@didntduck.org \
--cc=bvadapal@vt.edu \
--cc=linux-kernel@vger.kernel.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