From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] register_blkdev
Date: 8 Mar 2003 13:26:37 -0800 [thread overview]
Message-ID: <b4dn6d$go8$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030308194331.A31291@infradead.org
Followup to: <20030308194331.A31291@infradead.org>
By author: Christoph Hellwig <hch@infradead.org>
In newsgroup: linux.dev.kernel
>
> So people should have started working on it sooner. If people really think
> they need a 32bit dev_t for their $BIGNUM of disks (and I still don't buy
> that argument) we should just introduce it and use it only for block devices
> (which already are fixed up for this) and stay with the old 8+8 split for
> character devices. Note that Linux is about doing stuff right, not fast.
>
We need it if anything even more for character devices. Character
devices are under even more allocation pressure, and just look at the
ugly hacks we've already had to play for e.g. tty devices.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-03-08 21:16 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 0:57 [PATCH] register_blkdev Andries.Brouwer
2003-03-08 0:53 ` Greg KH
[not found] ` <20030308073407.A24272@infradead.org>
2003-03-08 19:29 ` Greg KH
2003-03-08 19:43 ` Christoph Hellwig
2003-03-08 21:26 ` H. Peter Anvin [this message]
2003-03-08 21:55 ` Christoph Hellwig
2003-03-08 21:41 ` Joel Becker
2003-03-08 21:52 ` Christoph Hellwig
2003-03-08 22:16 ` Joel Becker
2003-03-08 22:21 ` Christoph Hellwig
2003-03-10 17:31 ` Joel Becker
2003-03-08 23:37 ` Alan Cox
2003-03-08 22:36 ` Linus Torvalds
2003-03-08 23:56 ` Alan Cox
2003-03-09 5:08 ` Gerrit Huizenga
2003-03-17 19:21 ` Steven Dake
-- strict thread matches above, loose matches on Subject: below --
2003-03-08 20:59 Andries.Brouwer
2003-03-08 21:09 ` Christoph Hellwig
2003-03-08 20:26 Andries.Brouwer
2003-03-08 20:31 ` Christoph Hellwig
2003-03-08 1:49 Andries.Brouwer
2003-03-07 19:50 Andries.Brouwer
2003-03-07 19:52 ` Christoph Hellwig
2003-03-07 19:32 Andries.Brouwer
2003-03-07 19:36 ` Christoph Hellwig
2003-03-07 20:30 ` Andrew Morton
2003-03-07 22:12 ` Greg KH
2003-03-07 22:33 ` Andrew Morton
2003-03-07 23:45 ` Greg KH
2003-03-08 1:14 ` Alan Cox
2003-03-08 0:50 ` Greg KH
2003-03-08 1:05 ` Andrew Morton
2003-03-08 1:03 ` Greg KH
2003-03-08 1:13 ` Linus Torvalds
2003-03-08 15:09 ` Alan Cox
2003-03-08 15:53 ` Christoph Hellwig
2003-03-09 2:02 ` Chris Wedgwood
2003-03-10 4:46 ` Oliver Xymoron
2003-03-08 15:11 ` Alan Cox
2003-03-08 19:37 ` Greg KH
2003-03-08 19:50 ` Christoph Hellwig
2003-03-08 20:00 ` Greg KH
2003-03-08 20:23 ` Christoph Hellwig
2003-03-07 22:55 ` Joel Becker
2003-03-07 22:57 ` Christoph Hellwig
2003-03-07 23:17 ` Randy.Dunlap
2003-03-07 23:38 ` John Cherry
2003-03-07 23:36 ` Christoph Hellwig
2003-03-07 23:46 ` Andrew Morton
2003-03-07 23:54 ` Christoph Hellwig
2003-03-08 1:49 ` Joel Becker
2003-03-08 1:58 ` Greg KH
2003-03-08 2:15 ` Joel Becker
2003-03-08 2:18 ` Linus Torvalds
2003-03-08 2:42 ` Joel Becker
2003-03-08 19:31 ` Greg KH
2003-03-08 21:39 ` Joel Becker
2003-03-08 21:59 ` Greg KH
2003-03-08 1:04 ` Alan Cox
2003-03-09 4:32 ` Horst von Brand
2003-03-09 5:11 ` Valdis.Kletnieks
2003-03-07 18:49 Andries.Brouwer
2003-03-07 19:06 ` Christoph Hellwig
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='b4dn6d$go8$1@cesium.transmeta.com' \
--to=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