From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-mm <linux-mm@kvack.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] Add MM_DEAD flag to struct mm_struct
Date: Fri, 27 Jul 2007 16:41:53 +1000 [thread overview]
Message-ID: <1185518513.5495.184.camel@localhost.localdomain> (raw)
In-Reply-To: <1185501659.5495.174.camel@localhost.localdomain>
On Fri, 2007-07-27 at 12:01 +1000, Benjamin Herrenschmidt wrote:
> Some architectures like sparc can do useful optimizations when knowing
> that an entire MM is being destroyed. At the moment, they rely on
> fullmm in the mmu_gather structure. However, that doesn't always work
> out very well with some of the changes we are doing. Among other things,
> the TLB flushing on sparc64 is done using per-CPU tracking data, making
> the batch not per-CPU will break that link.
>
> So instead, we add a new flag to struct mm_struct that indicates that
> the mm is going away, for those archs to use. It also allows to use it
> in situations (such as PTE ops) where the batch isn't accessible (or
> there is no batch)
And the patch forgets to clear it in mm_init ... will send a new one
later.
Cheers,
Ben.
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-27 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 2:00 Benjamin Herrenschmidt
2007-07-27 6:41 ` Benjamin Herrenschmidt [this message]
2007-07-27 7:13 ` [PATCH/RFC] Add MM_DEAD flag to struct mm_struct #2 Benjamin Herrenschmidt
2007-07-27 8:09 ` [PATCH/RFC] Add MM_DEAD flag to struct mm_struct #3 Benjamin Herrenschmidt
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=1185518513.5495.184.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--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