public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	clemens@ladisch.de, Yinghai Lu <yinghai@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH 4/4] PCI: pre-allocate additional resources to devices only after successful allocation of essential resources.
Date: Fri, 4 Mar 2011 10:47:30 -0800	[thread overview]
Message-ID: <20110304104730.09ded35f@jbarnes-desktop> (raw)
In-Reply-To: <1297734200-23327-5-git-send-email-linuxram@us.ibm.com>

On Mon, 14 Feb 2011 17:43:20 -0800
Ram Pai <linuxram@us.ibm.com> wrote:

> Linux tries to pre-allocate minimal resources to hotplug bridges. This
>     works fine as long as there are enough resources  to satisfy all other
>     genuine resource requirements. However if enough resources are not
>     available to satisfy any of these nice-to-have pre-allocations, the
>     resource-allocator reports errors and returns failure.
> 
>     This patch distinguishes between must-have resource from nice-to-have
>     resource.  Any failure to allocate nice-to-have resources are ignored.
> 
>     This behavior can be particularly useful to trigger automatic
>     reallocation when the OS discovers genuine allocation-conflicts
>     or genuine unallocated-requests caused by buggy allocation behavior
>     of the native BIOS/uEFI.
> 
>     https://bugzilla.kernel.org/show_bug.cgi?id=15960 captures the movitation
>     behind the patch. This patch is verified to resolve the above bug.

Ok, applied this series.  Everyone please test thoroughly as resource
changes always seem to bite us.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2011-03-04 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  1:43 [PATCH 0/4] PCI: preallocate resource patch series Ram Pai
2011-02-15  1:43 ` [PATCH 1/4] PCI: refactor io size calculation code Ram Pai
2011-02-15  1:43 ` [PATCH 2/4] PCI: data structure agnostic free list function Ram Pai
2011-02-15  1:43 ` [PATCH 3/4] PCI: introduce reset_resource() Ram Pai
2011-02-25 22:56   ` Jesse Barnes
2011-02-15  1:43 ` [PATCH 4/4] PCI: pre-allocate additional resources to devices only after successful allocation of essential resources Ram Pai
2011-03-04 18:47   ` Jesse Barnes [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=20110304104730.09ded35f@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --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