From: Chris Mason <chris.mason@oracle.com>
To: linux-fsdevel@vger.kernel.org
Cc: akpm@osdl.org, zach.brown@oracle.com
Subject: Re: [RFC PATCH 0/2] O_DIRECT locking rework
Date: Tue, 24 Oct 2006 15:34:35 -0400 [thread overview]
Message-ID: <20061024193435.GE12815@think.oraclecorp.com> (raw)
In-Reply-To: <20061020183237.GA8674@think.oraclecorp.com>
Hello,
Here is a new cut of my O_DIRECT locking rework. It has a much lower
cpu cost than the last set, and simple benchmarks no longer show a
regression here in system time. But, the complexity for inserting
placeholder pages has gone up.
I've also changed the way I test for a place holder page (from
mm/filemap.c):
static struct address_space placeholder_address_space;
#define PagePlaceHolder(page) ((page)->mapping == &placeholder_address_space)
This is more stable than the last one but I'm just starting to run race
and load testing on it.
-chris
next prev parent reply other threads:[~2006-10-24 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:32 [RFC PATCH 0/2] O_DIRECT locking rework Chris Mason
2006-10-20 18:38 ` [RFC PATCH 1/2] placeholder pages Chris Mason
2006-10-20 18:41 ` [RFC PATCH 1/2] page cache locking for O_DIRECT Chris Mason
2006-10-20 19:30 ` [RFC PATCH 0/2] O_DIRECT locking rework Andrew Morton
2006-10-20 20:03 ` Zach Brown
2006-10-20 20:12 ` Chris Mason
2006-10-20 20:05 ` Chris Mason
2006-10-20 20:23 ` Andi Kleen
2006-10-24 19:34 ` Chris Mason [this message]
2006-10-24 19:38 ` [RFC PATCH 1/2] placeholder pages Chris Mason
2006-10-24 19:40 ` [RFC PATCH 2/2] O_DIRECT locking via placeholders Chris Mason
2006-10-24 20:28 ` [RFC PATCH 0/2] O_DIRECT locking rework Badari Pulavarty
2006-10-24 20:50 ` Chris Mason
2006-10-24 21:52 ` Badari Pulavarty
2006-10-24 22:22 ` Chris Mason
2006-10-24 22:47 ` Badari Pulavarty
2006-10-24 22:37 ` Russell Cattelan
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=20061024193435.GE12815@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zach.brown@oracle.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;
as well as URLs for NNTP newsgroup(s).