From: Shaya Potter <spotter@cs.columbia.edu>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: task_struct.mm == NULL
Date: 28 Nov 2001 09:10:30 -0500 [thread overview]
Message-ID: <1006956633.4222.2.camel@zaphod> (raw)
In-Reply-To: <p734rnfrsnb.fsf@amdsim2.suse.de>
In-Reply-To: <Pine.GSO.4.31.0111281300070.8642-100000@eduserv.rug.ac.be.suse.lists.linux. kernel> <p734rnfrsnb.fsf@amdsim2.suse.de>
On Wed, 2001-11-28 at 07:23, Andi Kleen wrote:
> Frank Cornelis <Frank.Cornelis@rug.ac.be> writes:
>
> > Hey,
> >
> > I found in some code checks for task_struct.mm being NULL.
> > When can task_struct.mm of a process be NULL except right before the
> > process-kill?
>
> For kernel threads that run in lazy-mm mode. It allows a much cheaper context
> switch into kernel threads.
oh. so not all kernel threades have mm == null. I used to think that
kernel threads ran in the kernel's address space, therefore there was no
point in having an mm struct as that just defines a virtual process
address space. What's this lazy_mm mode?
thanks,
shaya
next prev parent reply other threads:[~2001-11-28 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.31.0111281300070.8642-100000@eduserv.rug.ac.be.suse.lists.linux.kernel>
2001-11-28 12:23 ` task_struct.mm == NULL Andi Kleen
2001-11-28 14:10 ` Shaya Potter [this message]
2001-11-28 12:03 Frank Cornelis
2001-11-28 12:18 ` Tigran Aivazian
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=1006956633.4222.2.camel@zaphod \
--to=spotter@cs.columbia.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