linux-kernel - Re: [PATCH 00/25] dyn_array and nr

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]

Message-ID: <86802c440808051615h57baa06ci5ab040048786b50d@mail.gmail.com>
Date:	Tue, 5 Aug 2008 16:15:56 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Dhaval Giani" <dhaval@...ux.vnet.ibm.com>,
	"Mike Travis" <travis@....com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/25] dyn_array and nr_irqs support v3

On Tue, Aug 5, 2008 at 4:01 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Yinghai Lu wrote:
>>
>> Peter, Andrew,
>>
>> Please check dyn_array support for x86
>> v3: split changing to nr_irqs to small patches
>>    fix checkpatch error
>>    reorder the patch sequence to make dyn_array support go at first
>>        so could use that with arrays other than NR_IRQS
>>
>
> The real issue is that I think Eric is right: the dyn_array is an
> interesting data structure, but it's the wrong solution for the problem.  A
> static array would have to be ridiculously large given the potential number
> of interrupt sources.
>

i am working on dyn_array + condense irq_desc/irq_cfg.

it will use dyn_array to allocate 32 entry for irq_desc/irq_cfg, and
will use get_irq_desc via list to distribute it. later if need more,
will allocate more 32 entries....

so will send out v4.

YH
--
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/