From: Nick Piggin <nickpiggin@yahoo.com.au>
To: davidm@hpl.hp.com
Cc: Ingo Molnar <mingo@elte.hu>,
"David S. Miller" <davem@davemloft.net>,
tony.luck@intel.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched: unlocked context-switches
Date: Wed, 13 Apr 2005 13:26:02 +1000 [thread overview]
Message-ID: <425C914A.3070604@yahoo.com.au> (raw)
In-Reply-To: <16988.477.530205.502023@napali.hpl.hp.com>
David Mosberger wrote:
>>>>>>On Tue, 12 Apr 2005 12:12:45 +1000, Nick Piggin <nickpiggin@yahoo.com.au> said:
>
>
> >> Now, Ingo says that the order is reversed with his patch, i.e.,
> >> switch_mm() happens after switch_to(). That means flush_tlb_mm()
> >> may now see a current->active_mm which hasn't really been
> >> activated yet.
>
> Nick> If that did bother you, could you keep track of the actually
> Nick> activated mm in your arch code? Or would that involve more
> Nick> arch hooks and general ugliness in the scheduler?
>
> I'm sorry, but I don't see the point of this. We are already tracking
> care of ownership, just not atomically. What's the point of putting
> another level of (atomic) tracking on top of it. That seems
> exceedingly ugly.
>
Well, you were worried about it not being atomic. So that would be
the point, but I agree it would probably be exceedingly ugly if
implemented.
Nick
next prev parent reply other threads:[~2005-04-13 3:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3R6Ir-89Y-23@gated-at.bofh.it>
2005-04-09 6:32 ` [patch] sched: unlocked context-switches David Mosberger-Tang
2005-04-09 7:07 ` Ingo Molnar
2005-04-09 7:15 ` David Mosberger
2005-04-09 22:58 ` David S. Miller
2005-04-10 6:43 ` Ingo Molnar
2005-04-12 1:06 ` David Mosberger
2005-04-12 2:12 ` Nick Piggin
2005-04-12 17:14 ` David Mosberger
2005-04-13 3:26 ` Nick Piggin [this message]
2005-04-12 6:42 ` Ingo Molnar
2005-04-12 17:15 ` David Mosberger
2005-04-08 18:38 Luck, Tony
2005-04-09 4:38 ` Ingo Molnar
2005-04-09 6:28 ` Nick Piggin
2005-04-09 6:55 ` Ingo Molnar
2005-04-09 7:11 ` Nick Piggin
2005-04-09 9:22 ` Benjamin Herrenschmidt
2005-04-09 22:46 ` David S. Miller
2005-04-10 7:23 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 12:16 Ingo Molnar
2005-04-29 9:09 ` Andrew Morton
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=425C914A.3070604@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=davem@davemloft.net \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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