From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, viro@math.psu.edu
Cc: adilger@turbolabs.com, arvest@orphansonfire.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.11 loses sda9
Date: Thu, 11 Oct 2001 22:11:11 GMT [thread overview]
Message-ID: <UTC200110112211.WAA33043.aeb@cwi.nl> (raw)
> Right now we have a big and fairly nasty mix of the stuff that can be
> turned in pointer to block device, pointer to character device _and_
> stuff that is used as numbers.
Not really. I don't know whether you ever tried the experiment
and compiled kdev_t as a pointer to a struct with two members
namely major and minor, where the struct is allocated by MKDEV().
Very few places break, and these places are very easy to fix.
Stuff that is used as numbers can be forgotten quickly.
It is not difficult at all to get a kernel up and running that has
kdev_t a pointer type.
> Moreover, allocation policy for these structures is a tricky beast.
Yes. I entirely agree. All the rest is a mechanical action.
(Or, more precisely, removable modules require freeing, and
freeing requires refcounting. It is the refcounting that is
work, more than the allocation.)
Andries
next reply other threads:[~2001-10-11 22:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 22:11 Andries.Brouwer [this message]
2001-10-11 22:26 ` 2.4.11 loses sda9 Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 0:07 Andries.Brouwer
2001-10-11 20:29 Andries.Brouwer
2001-10-11 20:54 ` Alexander Viro
2001-10-11 19:07 Andries.Brouwer
2001-10-11 19:19 ` Alexander Viro
2001-10-11 5:07 Alexander Viro
2001-10-11 5:20 ` arvest
2001-10-11 5:23 ` Alexander Viro
2001-10-11 5:45 ` arvest
2001-10-11 6:08 ` Andreas Dilger
2001-10-11 6:17 ` Alexander Viro
2001-10-11 16:41 ` arvest
2001-10-11 16:46 ` Ignacio Vazquez-Abrams
2001-10-11 16:50 ` Alexander Viro
2001-10-11 17:23 ` Alexander Viro
2001-10-11 18:22 ` Guest section DW
2001-10-11 18:25 ` Alexander Viro
2001-10-11 4:22 arvest
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=UTC200110112211.WAA33043.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=adilger@turbolabs.com \
--cc=arvest@orphansonfire.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.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