From: Stephen Williams <steve@icarus.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Linux Kernel Development <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: vm_operations (was: Re: release not called for my driver?)
Date: Tue, 04 Jan 2000 09:19:12 -0800 [thread overview]
Message-ID: <200001041719.JAA03724@icarus.com> (raw)
In-Reply-To: Message from Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de> of "Tue, 04 Jan 2000 08:35:34 +0100." <Pine.LNX.4.10.10001040816410.8982-100000@nightmaster.csn.tu-chemnitz.de>
As far as I can tell, the Linux kernel device driver interface is very
poorly documented. The Rubinni book is as close as one gets to documentation,
but that does not cover much of vm behavior, and certainly doesn't cover
the cases you and I are handling.
Example code may well be the best documentation (thanks, Alan) but a
driver for a complex dvice can get a bit opaque and what are really needed
are contrived and heavily commented examples.
Oh well, Linux drivers are part of my job description so I do have the
time to figure things out. It just would be nice if the people who add these
nifty-neato interfaces in the kernel actually took the time to describe
them.
--
Steve Williams "The woods are lovely, dark and deep.
steve@icarus.com But I have promises to keep,
steve@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.nl.linux.org/Linux-MM/
prev parent reply other threads:[~2000-01-04 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E125GRI-000221-00@the-village.bc.nu>
2000-01-04 7:35 ` Ingo Oeser
2000-01-04 17:19 ` Stephen Williams [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=200001041719.JAA03724@icarus.com \
--to=steve@icarus.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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