From: Badari Pulavarty <pbadari@us.ibm.com>
To: tzachar@cs.bgu.ac.il
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: get_blocks_t semantics
Date: Wed, 20 Jul 2005 20:14:37 -0700 [thread overview]
Message-ID: <42DF131D.1080802@us.ibm.com> (raw)
In-Reply-To: <1121868182.18164.9.camel@nexus.cs.bgu.ac.il>
Nir Tzachar wrote:
> hello list.
>
> can someone please explain the exact semantics the get_block_t function
> (which is passed to mpage_readpage(s)) should implement??
> i could not find any documentation, and existing code kind of baffled
> me...
>
> my current understanding goes like this:
> if the block is present, call map_bh on the bh, with the physical block
> number.
> else, if "create" is set, allocate a new block for the inode, and again
> update the new physical block number.
>
> is this all??
>
> thanks.
>
For a given file offset, get_block() function is supposed to return the
physical disk block# of the block. (and size of the block). If "create"
is one, it needs to allocate the block (if it doesn't already exist).
Makes sense ?
Thanks,
Badari
next prev parent reply other threads:[~2005-07-21 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 14:03 get_blocks_t semantics Nir Tzachar
2005-07-21 3:14 ` Badari Pulavarty [this message]
2005-07-21 6:46 ` Nir Tzachar
2005-07-21 22:40 ` Badari Pulavarty
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=42DF131D.1080802@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tzachar@cs.bgu.ac.il \
/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;
as well as URLs for NNTP newsgroup(s).