From: Roman Zippel <zippel@linux-m68k.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modules and the Interfaces who Love Them (Take I)
Date: Wed, 13 Nov 2002 20:02:29 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0211131430190.2109-100000@serv> (raw)
In-Reply-To: <20021113101924.104F92C0B0@lists.samba.org>
Hi,
On Wed, 13 Nov 2002, Rusty Russell wrote:
> Feedback appreciated. It's aimed at driver writers.
If that's your audience, I expect a very confused audience.
You can make it very simple: There are safe interfaces and there are
broken interfaces and you shall never write or use broken interfaces.
For the majority of driver writers that's good enough.
Any documentation about module writing should also include/point to a
chapter about resource management. The user has to understand anyway, by
whom the module resources are used, otherwise he has more problems than
just module unloading. Module management is just a small part of this
whole picture or could be part of it, but right now the current module
code is desperate attempt at keeping it out of it.
I would prefer if the user would be teached about proper resource
management at kernel level. As soon as the user gets that right he will
also have no problems to get module unloading right _if_ that would follow
the same rules, but currently it involves lots of black magic instead.
Rusty, I'm not impressed by the new module code, maybe I'm missing
something, but it doesn't fix anything and only encourages to write more
broken interfaces.
bye, Roman
next prev parent reply other threads:[~2002-11-13 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 10:17 Rusty Russell
2002-11-13 19:02 ` Roman Zippel [this message]
2002-11-14 3:34 ` Rusty Russell
2002-11-14 4:34 ` Jeff Garzik
2002-11-14 10:28 ` Roman Zippel
2002-11-14 11:00 ` Roman Zippel
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=Pine.LNX.4.44.0211131430190.2109-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®