From: Jeffrey Mahoney <jeffm@suse.com>
To: "Kathy KN (HK)" <kathy.kn@gmail.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Bryan Henderson <hbryan@us.ibm.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Access content of file via inodes
Date: Thu, 07 Apr 2005 02:47:43 -0400 [thread overview]
Message-ID: <4254D78F.9030705@suse.com> (raw)
In-Reply-To: <f8ad67b305040622251465a93f@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kathy KN (HK) wrote:
> Just wondering. Say, reiserfs/r4, how is it possible to access
> the tail which contain the data of the file, since most of our
> production boxes uses either reiserfs and/or reiser4.
Hi Kathy -
Using vfs_read or the page cache functions will allow you access to the
tail since they will map it in as part of the file. You'd only run into
that problem if you were trying to access the data block-by-block as you
were initially.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
jeffm@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFCVNeOLPWxlyuTD7IRAgTMAJ4r+LU63wgVL168eGC/9VUuov4fLQCeKvms
UqIr/gxdn60EzfTRpQsjGlo=
=wQ0F
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-04-07 6:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 1:23 Access content of file via inodes Kathy KN
2005-04-05 7:22 ` Christoph Hellwig
2005-04-05 17:53 ` Bryan Henderson
2005-04-06 1:27 ` Kathy KN (HK)
2005-04-06 1:53 ` Jeff Mahoney
2005-04-06 17:57 ` Bryan Henderson
2005-04-06 7:54 ` Anton Altaparmakov
2005-04-06 11:33 ` Anton Altaparmakov
2005-04-06 13:09 ` Jeffrey Mahoney
2005-04-07 5:25 ` Kathy KN (HK)
2005-04-07 6:47 ` Jeffrey Mahoney [this message]
2005-04-07 8:09 ` Anton Altaparmakov
2005-04-05 19:01 ` Jeff Mahoney
2005-04-06 1:32 ` Kathy KN (HK)
2005-04-06 1:50 ` Jeff Mahoney
2005-04-08 6:01 ` Kathy KN (HK)
2005-04-08 8:17 ` Anton Altaparmakov
2005-05-27 19:13 ` Martin Jambor
2005-05-28 15:57 ` Anton Altaparmakov
2005-05-28 21:44 ` Martin Jambor
2005-05-29 7:26 ` Anton Altaparmakov
2005-05-30 21:51 ` Martin Jambor
2005-05-30 22:19 ` Anton Altaparmakov
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=4254D78F.9030705@suse.com \
--to=jeffm@suse.com \
--cc=aia21@cam.ac.uk \
--cc=hbryan@us.ibm.com \
--cc=kathy.kn@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 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).