From: Andries.Brouwer@cwi.nl
To: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [CFT] more kdev_t-ectomy
Date: Mon, 21 Apr 2003 01:56:34 +0200 (MEST) [thread overview]
Message-ID: <UTC200304202356.h3KNuYK14756.aeb@smtp.cwi.nl> (raw)
> Of course it may be possible to avoid kernel-internal numbers altogether.
> Sometimes that is an improvement, sometimes not. Pointers are more
> complicated than numbers - they point at something that must be allocated
> and freed and reference counted. A number is like a pointer without the
> reference counting.
I guess the question is: is there any point to have three forms --
with necessary conversions between them -- or is it simpler to have
two forms and just use the more awkward dev_t form everywhere?
It doesnt matter much. I would not have introduced kdev_t just
for slightly more efficient dev_t handling. But we have it already.
It seems meaningless to go and replace it by something more awkward
and less efficient.
[But should anyone want: globally s/kdev_t/dev_t/ and a small edit
of kdev_t.h suffices.]
We do need a dev32_t for NFSv2 et al, though.
I don't know why.
Andries
next reply other threads:[~2003-04-20 23:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 23:56 Andries.Brouwer [this message]
2003-04-21 0:15 ` H. Peter Anvin
2003-04-21 0:35 ` viro
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 1:32 Andries.Brouwer
2003-04-21 3:54 ` H. Peter Anvin
2003-04-20 21:58 Andries.Brouwer
2003-04-20 22:35 ` viro
2003-04-20 21:17 Andries.Brouwer
2003-04-20 21:26 ` viro
2003-04-20 13:31 viro
2003-04-20 15:26 ` Muli Ben-Yehuda
2003-04-20 16:00 ` Andries Brouwer
2003-04-20 19:24 ` viro
2003-04-20 21:10 ` H. Peter Anvin
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=UTC200304202356.h3KNuYK14756.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®