From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: hugh@veritas.com, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: smp race fix between invalidate_inode_pages* and do_no_page
Date: Thu, 12 Jan 2006 23:47:26 -0800 [thread overview]
Message-ID: <20060112234726.676c3873.akpm@osdl.org> (raw)
In-Reply-To: <43C75834.3040007@yahoo.com.au>
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> (I guess reclaim might be one, but quite rare -- any other significant
> lock_page users that we might hit?)
The only time 2.6 holds lock_page() for a significant duration is when
bringing the page uptodate with readpage or memset.
The scalability risk here is 100 CPUs all faulting in the same file in the
same pattern. Like the workload which caused the page_table_lock splitup
(that was with anon pages). All the CPUs could pretty easily get into sync
and start arguing over every single page's lock.
next prev parent reply other threads:[~2006-01-13 7:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 19:37 smp race fix between invalidate_inode_pages* and do_no_page Andrea Arcangeli
2005-12-13 21:02 ` Andrew Morton
2005-12-13 21:14 ` Andrea Arcangeli
2005-12-16 13:51 ` Andrea Arcangeli
2006-01-10 6:24 ` Andrea Arcangeli
2006-01-10 6:48 ` Andrea Arcangeli
2006-01-11 4:08 ` Nick Piggin
2006-01-11 8:23 ` Andrea Arcangeli
2006-01-11 8:51 ` Andrew Morton
2006-01-11 9:02 ` Andrea Arcangeli
2006-01-11 9:06 ` Andrew Morton
2006-01-11 9:13 ` Andrea Arcangeli
2006-01-11 20:49 ` Hugh Dickins
2006-01-11 21:05 ` Andrew Morton
2006-01-13 7:35 ` Nick Piggin
2006-01-13 7:47 ` Andrew Morton [this message]
2006-01-13 10:37 ` Nick Piggin
2006-03-31 12:36 ` Andrea Arcangeli
2006-04-02 5:17 ` Nick Piggin
2006-04-02 5:21 ` Andrew Morton
2006-04-07 19:18 ` Hugh Dickins
2006-01-11 9:39 ` Nick Piggin
2006-01-11 9:34 ` Nick Piggin
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=20060112234726.676c3873.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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;
as well as URLs for NNTP newsgroup(s).