linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation mm.h + swap.h
Date: Fri, 09 Mar 2001 00:39:40 +0000	[thread overview]
Message-ID: <5.0.2.1.2.20010309003257.00abeac0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0103081807260.1314-100000@duckman.distro.con ectiva>

At 21:10 08/03/2001, Rik van Riel wrote:
>+ * There is also a hash table mapping (inode,offset) to the page
>+ * in memory if present. The lists for this hash table use the fields
>+ * page->next_hash and page->pprev_hash.

Shouldn't (inode,offset) be (inode,index), or possibly (mapping,index)?

>+ * For choosing which pages to swap out, inode pages carry a
>+ * PG_referenced bit, which is set any time the system accesses
>+ * that page through the (inode,offset) hash table. This referenced

And here, too?

I know these are small details, but just for completeness sake...

Best regards,

         Anton


-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/

--
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/

       reply	other threads:[~2001-03-09  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0103081807260.1314-100000@duckman.distro.con ectiva>
2001-03-09  0:39 ` Anton Altaparmakov [this message]
2001-03-09 22:22   ` Rik van Riel
2001-03-08 21:10 Rik van Riel
2001-03-09  8:15 ` Philipp Rumpf
2001-03-09 22:39   ` Rik van Riel

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=5.0.2.1.2.20010309003257.00abeac0@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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