From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Rik van Riel <riel@conectiva.com.br>,
Andrew Morton <andrewm@uow.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: Questions - Re: [PATCH] documentation for mm.h
Date: Thu, 8 Mar 2001 11:51:37 +0100 [thread overview]
Message-ID: <20010308115137.M27675@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0103071931400.1409-100000@duckman.distro.con ectiva> <5.0.2.1.2.20010308095213.00a59040@pop.cus.cam.ac.uk>
In-Reply-To: <5.0.2.1.2.20010308095213.00a59040@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Thu, Mar 08, 2001 at 10:11:50AM +0000
On Thu, Mar 08, 2001 at 10:11:50AM +0000, Anton Altaparmakov wrote:
> 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):
isn't. To get the byte offset, you have to multiply it by PAGE_{CACHE_,}SIZE.
> [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?
Depends on the method of the driver, that is getting called.
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
next prev parent reply other threads:[~2001-03-08 10:52 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
2001-03-08 10:51 ` Ingo Oeser [this message]
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=20010308115137.M27675@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=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®