From: William Lee Irwin III <wli@holomorphy.com>
To: Zach Brown <zab@zabbo.net>
Cc: Andrew Morton <akpm@digeo.com>,
paulmck@us.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mjbligh@us.ibm.com
Subject: Re: [RFC][PATCH] Interface to invalidate regions of mmaps
Date: Tue, 13 May 2003 16:26:59 -0700 [thread overview]
Message-ID: <20030513232659.GC8978@holomorphy.com> (raw)
In-Reply-To: <3EC17BA3.7060403@zabbo.net>
On Tue, May 13, 2003 at 04:11:31PM -0700, Zach Brown wrote:
> but on the other hand, this doesn't solve another problem we have with
> opportunistic lock extents and sparse page cache populations. Ideally
> we'd like a FS specific pointer in struct page so we can associate pages
> in the cache with a lock, but I can't imagine suggesting such a thing
> within earshot of wli. so we'd still have to track the dirty offsets to
> avoid having to pass through offsets 0 ... i_size only to find that one
> page in the 8T file that was cached.
Nah, don't worry about sizeof(struct page) anymore; I'll just jack up
PAGE_SIZE to compensate.
-- wli
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Zach Brown <zab@zabbo.net>
Cc: Andrew Morton <akpm@digeo.com>,
paulmck@us.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mjbligh@us.ibm.com
Subject: Re: [RFC][PATCH] Interface to invalidate regions of mmaps
Date: Tue, 13 May 2003 16:26:59 -0700 [thread overview]
Message-ID: <20030513232659.GC8978@holomorphy.com> (raw)
In-Reply-To: <3EC17BA3.7060403@zabbo.net>
On Tue, May 13, 2003 at 04:11:31PM -0700, Zach Brown wrote:
> but on the other hand, this doesn't solve another problem we have with
> opportunistic lock extents and sparse page cache populations. Ideally
> we'd like a FS specific pointer in struct page so we can associate pages
> in the cache with a lock, but I can't imagine suggesting such a thing
> within earshot of wli. so we'd still have to track the dirty offsets to
> avoid having to pass through offsets 0 ... i_size only to find that one
> page in the 8T file that was cached.
Nah, don't worry about sizeof(struct page) anymore; I'll just jack up
PAGE_SIZE to compensate.
-- wli
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-13 23:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:36 [RFC][PATCH] Interface to invalidate regions of mmaps Paul E. McKenney
2003-05-13 22:00 ` William Lee Irwin III
2003-05-13 22:00 ` William Lee Irwin III
2003-05-13 22:21 ` Andrew Morton
2003-05-13 22:21 ` Andrew Morton
2003-05-13 22:43 ` Paul E. McKenney
2003-05-13 22:43 ` Paul E. McKenney
2003-05-13 23:11 ` Zach Brown
2003-05-13 23:19 ` Andrew Morton
2003-05-13 23:19 ` Andrew Morton
2003-05-13 23:57 ` Zach Brown
2003-05-13 23:26 ` William Lee Irwin III [this message]
2003-05-13 23:26 ` William Lee Irwin III
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=20030513232659.GC8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjbligh@us.ibm.com \
--cc=paulmck@us.ibm.com \
--cc=zab@zabbo.net \
/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.