linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-mm@kvack.org
Subject: Re: shpte scheduling-inside-spinlock bug
Date: Tue, 31 Dec 2002 11:02:30 -0600	[thread overview]
Message-ID: <62480000.1041354150@[10.1.1.5]> (raw)
In-Reply-To: <3E0ECC02.6CEBD613@digeo.com>

--On Sunday, December 29, 2002 02:18:42 -0800 Andrew Morton
<akpm@digeo.com> wrote:

> We would like to not hold i_shared_lock across the zap_pte_range() call
> anyway, for scheduling latency reasons.
> 
> But I suspect that i_shared_lock is the only thing which prevents the
> vma from disappearing while truncate is playing with it.
> 
> umm...  I think we can just turn i_shared_lock into a semaphore.  Nests
> inside mmap_sem.

I've stared at this for a couple of days and don't see any better solution.

Dave McCracken

--
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/

      parent reply	other threads:[~2002-12-31 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 10:18 Andrew Morton
2002-12-29 11:11 ` Andrew Morton
2002-12-31 17:02 ` Dave McCracken [this message]

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='62480000.1041354150@[10.1.1.5]' \
    --to=dmccr@us.ibm.com \
    --cc=akpm@digeo.com \
    --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