public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Bob Picco <bpicco@redhat.com>,
	Brian Bloniarz <phunge0@hotmail.com>,
	Charles Butterfield <charles.butterfield@nextcentury.com>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	linux-pci@vger.kernel.org,
	"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Stefan Becker <chemobejk@gmail.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	Fabrice Bellet <fabrice@bellet.info>,
	Yinghai Lu <yinghai@kernel.org>,
	Leann Ogasawara <leann.ogasawara@canonical.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 9/9] x86: allocate space within a region top-down
Date: Wed, 27 Oct 2010 08:23:54 +0200	[thread overview]
Message-ID: <20101027062354.GA6854@elte.hu> (raw)
In-Reply-To: <20101026153455.0fe4847f@jbarnes-desktop>


* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Tue, 26 Oct 2010 15:41:54 -0600
> Bjorn Helgaas <bjorn.helgaas@hp.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@hp.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...

It also appears to fix a serious compatibility bug (and a v2.6.34 regression), so 
even without extensive distro testing it's wise to push this upstream ASAP IMHO ...

Thanks,

	Ingo

      reply	other threads:[~2010-10-27  6:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 21:41 [PATCH v5 0/9] PCI: allocate space top-down, not bottom-up Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 1/9] resources: add a default alignf to simplify find_resource() Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 2/9] resources: factor out resource_clip() " Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 3/9] resources: ensure callback doesn't allocate outside available space Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 4/9] resources: handle overflow when aligning start of available area Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 5/9] resources: support allocating space within a region from the top down Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 6/9] PCI: allocate bus resources " Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 7/9] x86/PCI: allocate space from the end of a region, not the beginning Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 8/9] x86: update iomem_resource end based on CPU physical address capabilities Bjorn Helgaas
2010-10-26 21:41 ` [PATCH v5 9/9] x86: allocate space within a region top-down Bjorn Helgaas
2010-10-26 22:34   ` Jesse Barnes
2010-10-27  6:23     ` Ingo Molnar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101027062354.GA6854@elte.hu \
    --to=mingo@elte.hu \
    --cc=bjorn.helgaas@hp.com \
    --cc=bpicco@redhat.com \
    --cc=cebbert@redhat.com \
    --cc=charles.butterfield@nextcentury.com \
    --cc=chemobejk@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=fabrice@bellet.info \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=leann.ogasawara@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=phunge0@hotmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vonbrand@inf.utfsm.cl \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox