public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy Linton" <jlinton@interactivesi.com>
To: <mingo@elte.hu>
Cc: "Anton Blanchard" <anton@samba.org>, <linux-kernel@vger.kernel.org>
Subject: Re: highmem-2.4.7-A0 [Re: kmap() while holding spinlock]
Date: Thu, 26 Jul 2001 13:25:04 -0500	[thread overview]
Message-ID: <00bc01c11600$4c3901a0$bef7020a@mammon> (raw)
In-Reply-To: <Pine.LNX.4.33.0107261423020.3796-200000@localhost.localdomain>

> > [...] or to do the clearing (and copying) speculatively, after
> > allocating the page but before locking the pagetable lock. This might
> > lead to a bit more work in the pagefault-race case, but we dont care
> > about that window. It will on the other hand reduce pagetable_lock
> > contention (because the clearing/copying is done outside the lock), so
> > perhaps this solution is better.
>
> the attached highmem-2.4.7-A0 patch implements this method in both
> affected functions. Comments?
    It seems to me that the problem is more fundamental than that. Excuse my
ignorance, but what keeps the 'old_page' (and associated pte, checked two
lines down) from disappearing somewhere between the lock drop, alloc page
and the copy from the old page? Normally if this happens it appears the new
page gets dropped and the fault occurs again, and is resolved in a
potentially different way.



                                                                    jlinton



  reply	other threads:[~2001-07-26 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 20:12 kmap() while holding spinlock Anton Blanchard
2001-07-26 12:17 ` Ingo Molnar
2001-07-26 12:29   ` highmem-2.4.7-A0 [Re: kmap() while holding spinlock] Ingo Molnar
2001-07-26 18:25     ` Jeremy Linton [this message]
2001-07-26 19:50       ` Hugh Dickins

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='00bc01c11600$4c3901a0$bef7020a@mammon' \
    --to=jlinton@interactivesi.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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