From: Roger Luethi <rl@hellgate.ch>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC] State of ru_majflt
Date: Mon, 13 Oct 2003 18:51:04 +0200 [thread overview]
Message-ID: <20031013165104.GA14720@k3.hellgate.ch> (raw)
The ru_majflt field of struct rusage doesn't return major page faults --
pages retrieved from cache are counted as well. POSIX and Linux man pages
don't seem to cover that particular field, but the values returned are
neither what BSD (where Linux got its copy of the struct from) does nor
what the field name suggests.
A proper solution would probably have filemap_nopage tell its caller the
correct return code. Is this considered a bug or is it a documentation
issue? How much do we care?
Roger
--
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 reply other threads:[~2003-10-13 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 16:51 Roger Luethi [this message]
2003-10-13 18:51 ` Rik van Riel
2003-10-13 23:59 ` 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=20031013165104.GA14720@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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