mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andrew Morton <andrewm@uow.edu.au>, <linux-kernel@vger.kernel.org>
Subject: Questions - Re: [PATCH] documentation for mm.h
Date: Thu, 08 Mar 2001 10:11:50 +0000	[thread overview]
Message-ID: <5.0.2.1.2.20010308095213.00a59040@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0103071931400.1409-100000@duckman.distro.con ectiva>

At 22:33 07/03/2001, Rik van Riel wrote:
[snip]
>  typedef struct page {
>+       struct list_head list;          /* ->mapping has some page lists. */
>+       struct address_space *mapping;  /* The inode (or ...) we belong to. */
>+       unsigned long index;            /* Our offset within mapping. */

Assuming index is in bytes (it looks like it is): Shouldn't index of type 
unsigned long long or __u64? Otherwise, AFAICS using the page cache 
automatically results in an artificial 4Gib limit on file size, which is 
not very good, even by todays standards.

[snip]
>+ * During disk I/O, PG_locked is used. This bit is set before I/O
>+ * and reset when I/O completes. page->wait is a wait queue of all
>+ * tasks waiting for the I/O on this page to complete.

Is this physical I/O only or does it include a driver writing/reading the page?

Thanks,

         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/


       reply	other threads:[~2001-03-08 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0103071931400.1409-100000@duckman.distro.con ectiva>
2001-03-08 10:11 ` Anton Altaparmakov [this message]
2001-03-08 10:51   ` Ingo Oeser
2001-03-08 13:26     ` Question: fs meta data, page cache and locking Anton Altaparmakov
2001-03-08 14:59       ` Alexander Viro
2001-03-08 12:24   ` Questions - Re: [PATCH] documentation for mm.h Rik van Riel
2001-03-08 11:39 ` Anton Altaparmakov
2001-03-08 12:25   ` Rik van Riel
2001-03-08 12:41   ` Ingo Oeser

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.20010308095213.00a59040@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®