All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Address space operations questions
Date: Wed, 30 Mar 2005 00:30:55 +0200	[thread overview]
Message-ID: <8e70aacf05032914306a827923@mail.gmail.com> (raw)
In-Reply-To: <8e70aacf05032616151c958eed@mail.gmail.com>

Hi,

I have problems understanding the purpose of different entries of
struc address_space_operations in 2.6 kernels:

1. What is bmap for and what is it supposed to do?

2. What is the difference between sync_page and write_page?

3. What exactly (fs independent) is the relation in between
write_page, prepare_write and commit_write? Does prepare make sure a
page can be written (like allocating space), commit mark it dirty a
write write it sometime later on?

Thak you very much for any insight,

Martin

P.S.: I have dedicated a lot of time searching for any documentation,
tried IRC forums and even bought a book without getting a truly good
answer to the above questions. Oh yeah, I read a lot of the source
even though not all of it yet :-) On the other hand, if you find this
question inappropriate for this mailing list (too basic, perhaps),
please let me know.

       reply	other threads:[~2005-03-29 22:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8e70aacf05032616151c958eed@mail.gmail.com>
2005-03-29 22:30 ` Martin Jambor [this message]
2005-03-30 13:55   ` Address space operations questions Nikita Danilov
2005-03-31 19:59     ` Bryan Henderson
2005-03-31 20:43       ` Zach Brown
2005-03-31 21:40         ` Bryan Henderson
2005-03-31 21:53           ` Trond Myklebust
2005-04-01  0:06             ` Bryan Henderson
2005-04-06 23:52     ` Martin Jambor
2005-04-07  8:23       ` Nikita Danilov
2005-04-17 20:21         ` Lilo requirements (Was: Re: Address space operations questions) Martin Jambor
2005-04-17 21:33           ` Nikita Danilov
2005-04-18 17:33             ` Bryan Henderson
2005-04-07 16:58       ` Address space operations - >bmap Bryan Henderson

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=8e70aacf05032914306a827923@mail.gmail.com \
    --to=jamborm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.