public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Remco Treffkorn <remco@rvt.com>
Cc: "David S. Miller" <davem@redhat.com>,
	dan@embeddededge.com, benh@kernel.crashing.org,
	trini@kernel.crashing.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: 3 Serial issues up for discussion
Date: Tue, 30 Jul 2002 19:51:16 +0100	[thread overview]
Message-ID: <20020730195116.E7677@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200207301123.48322.remco@rvt.com>; from remco@rvt.com on Tue, Jul 30, 2002 at 11:23:47AM -0700

On Tue, Jul 30, 2002 at 11:23:47AM -0700, Remco Treffkorn wrote:
> The given solution presents almost zero overhead, but has the mentioned 
> problem. There is a way to allocate and free minor numbers, but that requires 
> storage. It could be handled like the fd_set's select uses. Just a bit field. 
> Bit cleared == minor available, bit set == in use.

core.c already knows which "slots" are in use and which aren't, so
allocation and freeing of minor numbers isn't that much of a problem.

The sole purpose behind this is to solicit is peoples opinions and
ideas on those three points I've raised.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2002-07-30 18:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29  4:08 Serial core problems on embedded PPC David Gibson
2002-07-29  9:00 ` Russell King
2002-07-29 14:44   ` Tom Rini
2002-07-29 17:17     ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Russell King
2002-07-29 17:43       ` Tom Rini
2002-07-29 18:13         ` Benjamin Herrenschmidt
2002-07-29 19:07           ` Tom Rini
2002-07-29 19:09           ` 3 Serial issues up for discussion (was: " Dan Malek
2002-07-29 19:46             ` Remco Treffkorn
2002-07-29 20:18               ` Russell King
2002-07-30  2:54               ` 3 Serial issues up for discussion David S. Miller
2002-07-30 18:23                 ` Remco Treffkorn
2002-07-30 18:47                   ` Nicolas Pitre
2002-07-30 18:51                   ` Russell King [this message]
2002-07-30 18:44                 ` Nicolas Pitre
2002-07-29 18:15         ` 3 Serial issues up for discussion (was: Re: Serial core problems on embedded PPC) Matt Porter
2002-07-29 17:47       ` [parisc-linux] " Christoph Plattner
2002-07-29 22:19       ` Matthew Wilcox
2002-07-30 14:36         ` Stuart MacDonald
2002-07-30 15:19           ` Matthew Wilcox
2002-07-30 15:43             ` Stuart MacDonald
2002-07-30 15:53               ` Russell King
2002-07-30 15:59                 ` Greg KH
2002-07-30 16:06                 ` Stuart MacDonald
2002-08-02  1:57         ` Jeff Randall
2002-07-30  2:51       ` 3 Serial issues up for discussion David S. Miller
2002-07-30  1:12   ` Serial core problems on embedded PPC David Gibson

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=20020730195116.E7677@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=remco@rvt.com \
    --cc=trini@kernel.crashing.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