From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Ram Pai <linuxram@us.ibm.com>,
torvalds@linux-foundation.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, yinghai@kernel.org
Subject: Re: [PATCH] PCI: conditional resource-reallocation through kernel parameter pci=realloc
Date: Thu, 30 Jun 2011 10:07:05 -0700 [thread overview]
Message-ID: <20110630100705.2d65656c@jbarnes-desktop> (raw)
In-Reply-To: <4E0CACB7.7040709@hartkopp.net>
On Thu, 30 Jun 2011 19:04:55 +0200
Oliver Hartkopp <socketcan@hartkopp.net> wrote:
> On 30.06.2011 10:09, Ram Pai wrote:
> > Multiple attempts to dynamically reallocate pci resources have unfortunately
> > lead to regressions. Though we continue to fix the regressions and fine tune the
> > dynamic-reallocation behavior, we have not reached a acceptable state yet.
> >
> > This patch provides a interim solution. It disables dynamic-reallocation; by
> > default, with the ability to enable it through pci=realloc kernel command line
> > parameter.
>
> What is the advantage of creating an 'interim' kernel parameter instead of
> reverting the problematic commit and queue up a proper solution for 3.1 ?
>
> A kernel parameter needs to be observed, documented and set appropriately.
>
> I would prefer to have an automatic solution - if not in 3.0 then in 3.1 ...
Yeah, we all want an automatic solution, but we still haven't been able
to achieve one. My hope is that a parameter will let us keep the code
upstream for Ram and others to keep fixing, then we can move to using
it by default in some future release. Keeping the code upstream but
behind a param should make development easier; at least that's the goal.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-06-30 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 8:09 [PATCH] PCI: conditional resource-reallocation through kernel parameter pci=realloc Ram Pai
2011-06-30 17:04 ` Oliver Hartkopp
2011-06-30 17:07 ` Jesse Barnes [this message]
2011-06-30 17:12 ` Oliver Hartkopp
2011-06-30 18:38 ` Ram Pai
2011-06-30 20:24 ` Bjorn Helgaas
2011-06-30 20:26 ` Jesse Barnes
2011-07-06 9:06 ` Ram Pai
2011-07-06 16:07 ` Jesse Barnes
2011-07-07 1:00 ` Stephen Rothwell
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=20110630100705.2d65656c@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=socketcan@hartkopp.net \
--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