linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: page cache KPI
Date: Mon, 21 Jul 2008 09:18:41 +0200	[thread overview]
Message-ID: <38b2ab8a0807210018r16839693p8cf47e6ea0f08d4e@mail.gmail.com> (raw)

Hello,

Kernel core code is usually great and well designed IMHO.

But here I find the page cache KPI really incosistent in its routine
names. For example, here are different helpers I could find:

page_cache_get()
page_cache_release()
page_cache_alloc()

find_get_page()
find_lock_page()

grab_cache_page()
grab_cache_page_nowait()

read_cache_page_async()
read_cache_page()

add_to_page_cache()
remove_from_page_cache()

lock_page()
wait_on_page_writeback()
...

Do these inconsistencies exist for historical reasons or am I missing
something ?

If I am right, wouldn't it better for them to start with page_cache_
or something
similar.

Thanks
-- 
Francis

                 reply	other threads:[~2008-07-21  7:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=38b2ab8a0807210018r16839693p8cf47e6ea0f08d4e@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=linux-fsdevel@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 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).