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: <20101026153455.0fe4847f@jbarnes-desktop>
Date:	Tue, 26 Oct 2010 15:34:55 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Bob Picco <bpicco@...hat.com>,
	Brian Bloniarz <phunge0@...mail.com>,
	Charles Butterfield <charles.butterfield@...tcentury.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, linux-pci@...r.kernel.org,
	"Horst H. von Brand" <vonbrand@....utfsm.cl>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Stefan Becker <chemobejk@...il.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	Fabrice Bellet <fabrice@...let.info>,
	Yinghai Lu <yinghai@...nel.org>,
	Leann Ogasawara <leann.ogasawara@...onical.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v5 9/9] x86: allocate space within a region top-down

On Tue, 26 Oct 2010 15:41:54 -0600
Bjorn Helgaas <bjorn.helgaas@...com> wrote:

> 
> Request that allocate_resource() use available space from high addresses
> first, rather than the default of using low addresses first.
> 
> The most common place this makes a difference is when we move or assign
> new PCI device resources.  Low addresses are generally scarce, so it's
> better to use high addresses when possible.  This follows Windows practice
> for PCI allocation.
> 
> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228#c42
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com>
> ---

Ok, applied this version to -next.  It's been going through distros and
lots of testing despite a lack of recent coverage in PCI -next, so I'm
planning to send it to Linus this week.  We probably won't catch much
more until it hits his tree anyway...

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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