From: "Stephen C. Tweedie" <sct@redhat.com>
To: Vladimir Dergachev <vladimid@seas.upenn.edu>
Cc: linux-mm@kvack.org
Subject: Re: VFS buffer monitoring
Date: Wed, 19 Aug 1998 13:01:41 +0100 [thread overview]
Message-ID: <199808191201.NAA00882@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <199808181530.LAA23097@blue.seas.upenn.edu>
Hi,
On Tue, 18 Aug 1998 11:30:59 -0400 (EDT), "Vladimir Dergachev"
<vladimid@seas.upenn.edu> said:
> 2) I looked around in the kernel source and it looks to me that
> this stuff isn't visible outside of kernel..
Yep.
> So should I just go and change kernel directly or can I still
> get by with writing a module ? (or maybe even better , just
> an ordinary program ? )
You'll need to modify the kernel (linux/fs/buffer.c); the buffer lookup
information is not exported to modules.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
prev parent reply other threads:[~1998-08-19 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-18 15:30 Vladimir Dergachev
1998-08-19 12:01 ` Stephen C. Tweedie [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=199808191201.NAA00882@dax.dcs.ed.ac.uk \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=vladimid@seas.upenn.edu \
/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