From: Grant Grundler <iod00d@hp.com>
To: Sean Hefty <mshefty@ichips.intel.com>
Cc: Roland Dreier <rdreier@cisco.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [openib-general] [PATCH 5/5] [RFC] Infiniband: connection abstraction
Date: Wed, 18 Jan 2006 10:49:45 -0800 [thread overview]
Message-ID: <20060118184945.GG6818@esmail.cup.hp.com> (raw)
In-Reply-To: <43CE8695.9080401@ichips.intel.com>
On Wed, Jan 18, 2006 at 10:19:01AM -0800, Sean Hefty wrote:
> Roland Dreier wrote:
> > > + UCMA_MAX_BACKLOG = 128
> >
> >Is there any reason that we might want to make this a tunable? Maybe
> >as a module parameter that's writable in sysfs...
>
> There's no reason not to make this tunable.
Yes, there are reasons to NOT make something a tunable:
o increases system complexity (admin)
o increases the amount of documentation (learning curve)
o increases test matrix/cost (devel/support cost)
o generally hurts performance (var vs a constant of the same value)
Any reason to make something a tunable has to compensate
for the above drawbacks. An answer to Roland's question
is a reasonable prerequisite if someone wants add a tunable.
IB doesn't have the much in /sys/class/infiniband* or module parameters
and I think that's a Good Thing.
grant
next prev parent reply other threads:[~2006-01-18 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 23:16 [PATCH 0/5] [RFC] Infiniband: connection abstraction Sean Hefty
2006-01-17 23:21 ` [PATCH 1/5] " Sean Hefty
2006-01-17 23:24 ` [PATCH 2/5] " Sean Hefty
2006-01-17 23:28 ` [PATCH 3/5] " Sean Hefty
2006-01-21 23:37 ` Roland Dreier
2006-01-17 23:37 ` [PATCH 4/5] " Sean Hefty
2006-01-17 23:44 ` [PATCH 5/5] " Sean Hefty
2006-01-18 15:43 ` Roland Dreier
2006-01-18 15:44 ` Roland Dreier
2006-01-18 18:19 ` Sean Hefty
2006-01-18 18:49 ` Grant Grundler [this message]
[not found] ` <ORSMSX401FRaqbC8wSA00000040@orsmsx401.amr.corp.intel.com>
2006-01-17 23:38 ` [PATCH 2/5] " Stephen Hemminger
2006-01-17 23:51 ` Sean Hefty
2006-01-18 7:08 ` Arjan van de Ven
2006-01-18 20:27 ` Bryan O'Sullivan
2006-01-18 2:03 ` Grant Grundler
2006-01-18 17:46 ` Sean Hefty
2006-01-18 18:02 ` Grant Grundler
2006-01-18 18:13 ` Sean Hefty
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=20060118184945.GG6818@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
/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).