From: Andrew Morton <akpm@osdl.org>
To: Jack Steiner <steiner@sgi.com>
Cc: davidm@hpl.hp.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Inefficient TLB flushing
Date: Wed, 12 Nov 2003 19:31:24 -0800 [thread overview]
Message-ID: <20031112193124.48224ccb.akpm@osdl.org> (raw)
In-Reply-To: <20031113031801.GA17689@sgi.com>
Jack Steiner <steiner@sgi.com> wrote:
>
> > Either that, or add a new interface function
> >
> > int mmu_gather_is_full_mm(mmu_gather *tlb);
> >
> > and use it...
> >
>
> How implementation independent should it be? Currently, there is only one
> field in the mmu_gather structure that must be preserved. However, if we
> want to make the interface truly implementation independent, it seems
> like we should define something like:
>
> if (need_resched()) {
> struct mmu_gather_state state;
> tlb_mmu_gather_save_state(*tlbp, &state);
> tlb_finish_mmu(*tlbp, tlb_start, start);
> ...
> *tlbp = tlb_mmu_gather_restore_state(&state);
> }
>
> Is this overkill?
Think so ;) The `full_mm_flush' boolean is the only state thing we can pass
into tlb_gather_mmu anyway.
>
> Should we use the patch given above for 2.6.0 & replace it with an implementation
> independent interface for 2.6.1?
Just the little wrapper which doesn't assume the presence of
mmu_gather.full_mm should suffice.
next prev parent reply other threads:[~2003-11-13 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 20:01 Inefficient TLB flushing Jack Steiner
2003-11-12 20:49 ` David Mosberger
2003-11-12 21:22 ` Andrew Morton
2003-11-13 3:18 ` Jack Steiner
2003-11-13 3:31 ` Andrew Morton [this message]
2003-11-13 3:56 ` David S. Miller
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=20031112193124.48224ccb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
/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