From: Zach Brown <zach.brown@oracle.com>
To: Andrew Morton <akpm@osdl.org>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org, adilger@clusterfs.com
Subject: Re: [RFC] page lock ordering and OCFS2
Date: Fri, 21 Oct 2005 14:57:47 -0700 [thread overview]
Message-ID: <4359645B.1080906@oracle.com> (raw)
In-Reply-To: <20051021135931.6065bbd1.akpm@osdl.org>
> All those games with PG_fs_misc look awfully similar to lock_page() - I'd
> have thought there's some room for rationalising code in there.
Yeah, it's very much like a secondary restricted page lock. Instead of
sleeping when you can't get the page lock, you can also try acquiring this sort
of secondary page lock bit which lets you do *very* specific things. Maybe
it's not *that* weird, I just didn't think that the core would be interested in
supporting that notion. I can try rolling a patch to see what a more sensible
API would look like.
> The overall approach would be to avoid adding overhead and complexity for
> other filesystems and to only export symbols which constitute a sensible
> API:
*nod*
- z
next prev parent reply other threads:[~2005-10-21 21:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 22:20 [RFC] page lock ordering and OCFS2 Zach Brown
2005-10-17 23:17 ` Andrew Morton
2005-10-18 0:40 ` Zach Brown
2005-10-18 1:24 ` Andrew Morton
2005-10-18 8:23 ` Anton Altaparmakov
2005-10-18 17:25 ` Zach Brown
2005-10-18 17:14 ` Zach Brown
2005-10-21 17:43 ` Zach Brown
2005-10-21 17:57 ` Christoph Hellwig
2005-10-21 20:36 ` Zach Brown
2005-10-21 20:59 ` Andrew Morton
2005-10-21 21:57 ` Zach Brown [this message]
2005-10-25 0:03 ` Zach Brown
2005-10-25 16:26 ` Zach Brown
2005-10-21 17:58 ` Andrew Morton
2005-10-21 20:32 ` Zach Brown
2005-10-17 23:37 ` Badari Pulavarty
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 20:13 Zach Brown
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=4359645B.1080906@oracle.com \
--to=zach.brown@oracle.com \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.