From: arjan@fenrus.demon.nl (Arjan van de Ven)
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-mm@kvack.org
Subject: Re: PATCH: rewrite of invalidate_inode_pages
Date: Fri, 12 May 2000 15:21:22 +0200 (CEST) [thread overview]
Message-ID: <m12qFNa-000OVtC@amadeus.home.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10005111445370.819-100000@penguin.transmeta.com> <yttya5ghhtr.fsf@vexeta.dc.fi.udc.es> <shsd7msemwu.fsf@charged.uio.no> <yttbt2chf46.fsf@vexeta.dc.fi.udc.es> <14619.16278.813629.967654@charged.uio.no> <ytt1z38acqg.fsf@vexeta.dc.fi.udc.es> <391BEAED.C9313263@sympatico.ca> <yttg0ro6lt8.fsf@vexeta.dc.fi.udc.es> <shs7ld0dj8x.fsf@charged.uio.no>
In article <shs7ld0dj8x.fsf@charged.uio.no> you wrote:
>>>>>> " " == Juan J Quintela <quintela@fi.udc.es> writes:
> > This was a first approach patch, if people like the thing
> > configurable, I can try to do that the weekend.
> Juan, Linus,
> Could you please look into changing the name of
> invalidate_inode_pages() to invalidate_pages_noblock() or something
> like that? Since NFS is the only place where this function is used, a
> change of name should not break any other code.
I'd vote for "invalidate_unlocked_inode_pages", as it also suggests
that the locked pages aren't invalidated.
Greetings,
Arjan van de Ven
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-05-12 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 21:40 Juan J. Quintela
2000-05-11 21:47 ` Linus Torvalds
2000-05-11 21:56 ` Juan J. Quintela
2000-05-11 22:22 ` Linus Torvalds
2000-05-12 1:01 ` Juan J. Quintela
2000-05-12 2:02 ` PATCH: new page_cache_get() (try 2) Juan J. Quintela
2000-05-11 22:22 ` PATCH: rewrite of invalidate_inode_pages Ingo Molnar
2000-05-11 22:34 ` Trond Myklebust
2000-05-11 22:54 ` Juan J. Quintela
2000-05-11 23:17 ` Trond Myklebust
2000-05-11 23:28 ` Juan J. Quintela
2000-05-11 23:55 ` Trond Myklebust
2000-05-12 11:28 ` John Cavan
2000-05-12 11:37 ` Juan J. Quintela
2000-05-12 12:51 ` Trond Myklebust
2000-05-12 13:21 ` Arjan van de Ven [this message]
2000-05-12 13:35 ` Trond Myklebust
2000-05-12 17:57 ` Juan J. Quintela
2000-05-12 13:30 ` Juan J. Quintela
2000-05-11 22:05 ` Jeff V. Merkey
2000-05-11 22:28 ` Trond Myklebust
2000-05-11 22:43 ` Juan J. Quintela
2000-05-11 22:56 ` Trond Myklebust
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=m12qFNa-000OVtC@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=linux-mm@kvack.org \
--cc=trond.myklebust@fys.uio.no \
/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