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: <48D7B5F8.9020300@sgi.com>
Date:	Mon, 22 Sep 2008 08:12:56 -0700
From:	Mike Travis <travis@....com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Rusty Russell <rusty@...tcorp.com.au>, Dean Nelson <dcn@....com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"H. Peter Anvin" <hpa@...or.com>, Jack Steiner <steiner@....com>,
	Alan Mayer <ajm@....com>, jeremy@...p.org,
	suresh.b.siddha@...el.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <Yinghai.lu@....com>
Subject: Re: [PATCH 1/3] switch vector_irq[] from irq number to irq_desc	pointer
 v2

Ingo Molnar wrote:
> * Mike Travis <travis@....com> wrote:
> 
>> Hi Ingo,
>>
>> Note that my recent patch from a couple of weeks ago, stripped almost 
>> all of the cpumask_t's from the io_apic functions.  Any chance we can 
>> apply them before we add more?
>>
>> I'd be willing to merge in Dean's patch over the top of mine (or 
>> vice-versa).
> 
> i'm really looking forwards to Rusty's 'get-rid-of-cpumask_t use' 
> patchset, which would solve such cpumask_t proliferation issues once and 
> for all.
> 
> 	Ingo

Hi Ingo,

The net effect of the "getting rid of cpumask_t's" will be the same.  This
patch reduces considerably the amount of stack space being required right
now.  The new cpumask_t approach will take quite a bit of time to get it
"up and running".  (It took me about a day to get init/main.c and kernel/sched.c
to just compile... it now needs the temp cpumasks to actually function.  And
there are a number of areas that will need to be altered before functional
testing can start.)

Thanks,
Mike
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ