From: "Theodore Ts'o" <tytso@mit.edu>
To: Christof <mail@pop2wap.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: some ext2-understanding problems (page cache etc.)
Date: Fri, 30 Apr 2004 16:29:15 -0400 [thread overview]
Message-ID: <20040430202915.GB23131@thunk.org> (raw)
In-Reply-To: <4091AA0F.8050700@pop2wap.net>
On Fri, Apr 30, 2004 at 03:21:19AM +0200, Christof wrote:
> Hello,
>
> I'm not a kernel guru, but my task is to extract some ext2-code from the
> kernel into user space for a scientific project/experiment. I've
> "ported" a lot of code by now but now I am stuck.
> I wanted to bypass the page cache and disk buffer and have all writes
> and reads directly in memory. I don't want to get into details, but
> imagine I have an image of an ext2-filesystem in memory and want to
> access it in user space but with the same interface as it would be in
> the kernel.
You're probably better off using the the libext2fs library that is
part of e2fsprogs, since it is already userspace code.
- Ted
prev parent reply other threads:[~2004-04-30 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 1:21 some ext2-understanding problems (page cache etc.) Christof
2004-04-30 20:29 ` Theodore Ts'o [this message]
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=20040430202915.GB23131@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@pop2wap.net \
/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