From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
<hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] opensm: Add initial congestion control configuration support
Date: Tue, 24 Jul 2012 19:58:25 +0300 [thread overview]
Message-ID: <20120724165825.GC2413@calypso> (raw)
In-Reply-To: <1342630767.18615.22.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
Hi Albert
> > > +
> > > + p_tbl = &p_osm->subn.port_guid_tbl;
> > > + p_next = cl_qmap_head(p_tbl);
> > > + while (p_next != cl_qmap_end(p_tbl)) {
> > > + osm_port_t *p_port = (osm_port_t *) p_next;
> > > + osm_node_t *p_node = p_port->p_node;
> > > + ib_api_status_t status;
> > > +
> > > + p_next = cl_qmap_next(p_next);
> > > +
> > > + if (osm_node_get_type(p_node) == IB_NODE_TYPE_SWITCH) {
> > > + status = cc_send_sw_cong_setting(&p_osm->sm, p_node);
> > > + if (status != IB_SUCCESS)
> > > + ret = -1;
> > > + } else if (osm_node_get_type(p_node) == IB_NODE_TYPE_CA) {
> > > + status = cc_send_ca_cong_setting(&p_osm->sm,
> > > + p_node,
> > > + p_port->p_physp);
> > > + if (status != IB_SUCCESS)
> > > + ret = -1;
> > > +
> > > + status = cc_send_cct(&p_osm->sm,
> > > + p_node,
> > > + p_port->p_physp);
> >
> > SetCongestionControlTable may also apply to enhanced port 0 of the switch.
>
> [AL] Got it.
This one can be postponed to a later patch. I'm not sure how much switches
support this mode.
> > > + p_opt->cc_cct.entries_len = 0;
> > > + p_opt->cc_cct.input_str = NULL;
> >
> > What about setting other CC defaults? It won't be enough for a user to just turn "congestion_control = TRUE" flag
> > for CC to work. Running with defaults won't be perfect, but CC will start to work.
>
> [AL] I initially didn't add it, as we were still trying to figure out
> optimal values for our situation w/ Lustre.
>
> How about we hold off on CC default values for another patch and
> discussion. It can be a very big discussion by itself. I think getting
> the core configuration support is more important presently.
>
Agreed.
-- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-24 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 21:19 [PATCH] opensm: Add initial congestion control configuration support Albert Chu
[not found] ` <1335302382.5973.132.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2012-07-17 15:33 ` Alex Netes
2012-07-18 16:59 ` Albert Chu
[not found] ` <1342630767.18615.22.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2012-07-24 16:58 ` Alex Netes [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-25 0:07 Albert Chu
[not found] ` <1343174826.18615.225.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2012-07-29 16:58 ` Alex Netes
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=20120724165825.GC2413@calypso \
--to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=chu11-i2BcT+NCU+M@public.gmane.org \
--cc=hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).