From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@lists.ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH 1/1] Add config option for batched hcalls
Date: Mon, 27 Sep 2010 15:06:46 -0500 [thread overview]
Message-ID: <1285618006.3016.27.camel@lexx> (raw)
In-Reply-To: <20100926034903.GA5473@lixom.net>
On Sat, 2010-09-25 at 22:49 -0500, Olof Johansson wrote:
> On Fri, Sep 24, 2010 at 04:44:15PM -0500, Will Schmidt wrote:
> >
> > Add a config option for the (batched) MULTITCE and BULK_REMOVE h-calls.
> >
> > By default, these options are on and are beneficial for performance and
> > throughput reasons. If disabled, the code will fall back to using less
> > optimal TCE and REMOVE hcalls. The ability to easily disable these
> > options is useful for some of the PREEMPT_RT related investigation and
> > work occurring on Power.
>
> Hi,
>
> I can see why it's useful to enable and disable, but these are all
> runtime-checked, wouldn't it be more useful to add a bootarg to handle
> it instead of adding some new config options that pretty much everyone
> will always go with the defaults on?
>
> The bits are set early, but from looking at where they're used, there
> doesn't seem to be any harm in disabling them later on when a bootarg
> is convenient to parse and deal with?
>
> It has the benefit of easier on/off testing, if that has any value for
> production debug down the road.
Hi Olof,
Thats a good idea, let me poke at this a bit more, see if I can get
bootargs for this.
Thanks,
-Will
>
>
> -Olof
>
next prev parent reply other threads:[~2010-09-27 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 21:44 [PATCH 1/1] Add config option for batched hcalls Will Schmidt
2010-09-26 3:49 ` Olof Johansson
2010-09-27 20:06 ` Will Schmidt [this message]
2010-09-28 17:02 ` [PATCH 1/1 v2 ] Add kernel parameter to disable " Will Schmidt
2010-09-28 17:52 ` Olof Johansson
2010-09-29 1:33 ` [PATCH 1/1 v3] " Will Schmidt
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=1285618006.3016.27.camel@lexx \
--to=will_schmidt@vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
/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;
as well as URLs for NNTP newsgroup(s).