linux-kernel - Re: [patch 2.6.25-rc5 1/2] gpiolib: dynamic gpio number allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 Mar 2008 16:28:03 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Brownell <david-b@...bell.net>
Cc:	linux-kernel@...r.kernel.org, avorontsov@...mvista.com
Subject: Re: [patch 2.6.25-rc5 1/2] gpiolib:  dynamic gpio number allocation

On Thu, 13 Mar 2008 15:18:58 -0800
David Brownell <david-b@...bell.net> wrote:

> On Thursday 13 March 2008, Andrew Morton wrote:
> 
> > hm.  I suppose that if someone want a huge number of GPIOs then we can
> > convert this to a bitmap or an IDR tree easily enough.
> 
> Actually, I tried IDRs for a while and they broke platforms
> which needed to initialize and use GPIOs early: before kmalloc
> would work.  A real PITA that was -- and slow too.

If IDRs were slow, that linear search will be glacial.

> 
> > Shouldn't ARCH_NR_GPIOS be CONFIG_NR_GPIOS?
> 
> No more than NR_IRQS is settable via Kconfig.  And for
> rather similar reasons.  :)

What are those reasons?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/