From: Andrew Morton <akpm@digeo.com>
To: paulmck@us.ibm.com
Cc: 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 15:21:41 -0700 [thread overview]
Message-ID: <20030513152141.5ab69f07.akpm@digeo.com> (raw)
In-Reply-To: <20030513133636.C2929@us.ibm.com>
"Paul E. McKenney" <paulmck@us.ibm.com> wrote:
>
> This patch adds an API to allow networked and distributed filesystems
> to invalidate portions of (or all of) a file. This is needed to
> provide POSIX or near-POSIX semantics in such filesystems, as
> discussed on LKML late last year:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103609089604576&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103167761917669&w=2
>
> Thoughts?
What filesystems would be needing this, and when could we see live code
which actually uses it?
> +/*
> + * Helper function for invalidate_mmap_range().
> + * Both hba and hlen are page numbers in PAGE_SIZE units.
> + */
> +static void
> +invalidate_mmap_range_list(struct list_head *head,
> + unsigned long const hba,
> + unsigned long const hlen)
Be nice to consolidate this with vmtruncate_list, so that it gets
exercised.
--
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 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:36 Paul E. McKenney
2003-05-13 22:00 ` William Lee Irwin III
2003-05-13 22:21 ` Andrew Morton [this message]
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:57 ` Zach Brown
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=20030513152141.5ab69f07.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjbligh@us.ibm.com \
--cc=paulmck@us.ibm.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