All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vu Pham <vuhuong-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Oren Duer <oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Arputham Benjamin <abenjamin-sJ/iWh9BUns@public.gmane.org>
Subject: Re: [PATCH] mlx4_core: enable changing HCA default max resource limits
Date: Tue, 22 Nov 2011 14:29:02 -0800	[thread overview]
Message-ID: <4ECC222E.8080209@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237316E9BE26-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hefty, Sean wrote:
>> Yeah, I guess it's sort of OK.  But is there really no better way to
>> handle this than making users deal with 7 more module parameters?

Do you have other suggestion?

We could have larger default profile which covers *most* known cases with the cost of memory for maintaining ICM page tables; however, there will be still some corner cases with large fabric.


> 
> Is it theoretically possible for these limits to change dynamically?

It requires extra code to clean up resources + reset HCA fw command (same thing to unload/reload driver)

> 
> Is there some easy way for nodes to discover the size of the fabric, so that drivers and applications can adjust their algorithms accordingly?  If not, would such a feature be useful enough to consider approaching the IBTA?
> 

I don't know if there is an easy way.

For in-band solution, query_sa for total port info records of the fabric would do; however, the driver first need to be up & running with some default profile, then it need to clean up and reset HCA with new learn profile. 

-vu
--
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

  parent reply	other threads:[~2011-11-22 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 17:39 [PATCH] mlx4_core: enable changing HCA default max resource limits vuhuong-VPRAkNaXOzVWk0Htik3J/w
     [not found] ` <20111108173940.GA23912-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-11-22 17:38   ` Vu Pham
     [not found]     ` <4ECBDE16.5040200-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-11-22 20:30       ` Roland Dreier
     [not found]         ` <CAL1RGDXBwDoXs-cRD4b+8WrS0eRzwAaVn4g4+_14YSAsxpkNbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-22 20:52           ` Hefty, Sean
     [not found]             ` <1828884A29C6694DAF28B7E6B8A8237316E9BE26-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-11-22 22:29               ` Vu Pham [this message]
2012-01-09 19:45               ` Roland Dreier

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=4ECC222E.8080209@mellanox.com \
    --to=vuhuong-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=abenjamin-sJ/iWh9BUns@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=oren-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.