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:	Wed, 12 Nov 2008 05:46:09 -0800
From:	Mike Travis <travis@....com>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Eric Dumazet <dada1@...mosbay.com>,
	Takashi Iwai <tiwai@...e.de>,
	Andreas Gruenbacher <agruen@...e.de>,
	Jan Blunck <jblunck@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Allocate module.ref array dynamically

Christoph Lameter wrote:
> On Tue, 11 Nov 2008, Mike Travis wrote:
> 
>> I haven't looked closely at Christoph's latest but I believe the x86_64 version
>> is waiting for the zero-based percpu variables (and hence the combined pda/percpu
>> base.)  It's on the queue just under 4k cpus.
> 
> The base cpu_alloc is indepedent. And your laziness on the zero based
> stuff only hurts the x86_64 version. Frankly, I think we should stop
> merging 4k patches until you have finished the work on zero based because
> that is elementary for various other things and simplifies 4k work. And it
> has been pending for more than 6 months now.
> 


Trust me, I would have finished it by now, but the most critical objective for me
(and hence the direction from my mgmt) is that SGI is able to ship UV systems when
they are ready, to customers who are buying them, to perform as they are expecting.
Nothing else comes close in priority.  I've already missed two merge windows,
missing a third and I may have to learn hara-kiri. ;-)  [And working up to 7 days
of 10-14+ hours per day, is not what one would normally think of as lazy.]

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