From: Christoph Hellwig <hch@infradead.org>
To: Andries.Brouwer@cwi.nl
Cc: akpm@digeo.com, alan@lxorguk.ukuu.org.uk, greg@kroah.com,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] register_blkdev
Date: Sat, 8 Mar 2003 20:31:46 +0000 [thread overview]
Message-ID: <20030308203146.A32002@infradead.org> (raw)
In-Reply-To: <UTC200303082026.h28KQFN04439.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Sat, Mar 08, 2003 at 09:26:15PM +0100
On Sat, Mar 08, 2003 at 09:26:15PM +0100, Andries.Brouwer@cwi.nl wrote:
> There is no need to do all of that. Going to 32-bit dev_t
> is trivial, not a major restructuring.
Doing it _right_ does require major restructuring.
> However, it can be crashed from userspace, so before we do
> the three minutes editing the audit is needed.
> Look at the patch for raw.c I posted a few hours ago.
> One trivial test.
And probably one of them in at least half of the character drivers. We need
to get rid of the artifical major/minor split completly instead of just
increasing it, leaving silly assumptions in and increasing the space consumed
by all those arrays by magnitudes.
> > If people really think they need a 32bit dev_t
> > we should just introduce it and use it only for block devices
> > and stay with the old 8+8 split for character devices.
>
> Of course discussing the future and how the cake should
> be divided once we have it may be of interest
No, the point is that the character devices aren't ready yet for moving
away from the old 8+8 split.
next prev parent reply other threads:[~2003-03-08 20:21 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 20:26 [PATCH] register_blkdev Andries.Brouwer
2003-03-08 20:31 ` Christoph Hellwig [this message]
-- 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 1:49 Andries.Brouwer
2003-03-08 0:57 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
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
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=20030308203146.A32002@infradead.org \
--to=hch@infradead.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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