From: Sebastian Riemer <sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Vasiliy Tolstov
<v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: tune ib stack
Date: Tue, 09 Apr 2013 16:37:09 +0200 [thread overview]
Message-ID: <51642795.1070208@profitbricks.com> (raw)
In-Reply-To: <5164245E.2030208-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 09.04.2013 16:23, Hal Rosenstock wrote:
>> So these values are exactly the same as in "ibv_devinfo" and can be set
>> in /sys/class/infiniband/mlx4_0/device/mlx4_port1_mtu.
>>
>> I've found the PortInfo with the command
>> "smpquery portinfo -C mlx4_0 3 1"
>> where I'm using the first HCA to contact the SM. I tell the SM the
>> destination LID ('3' here in my case) and the destination port ('1').
>>
>> Is there another method to set the max MTU?
>
> That doesn't set max MTU (MTUCap) but merely reads it (for that port).
Sorry, copy and paste error. I've meant the mlx4 file:
/sys/class/infiniband/mlx4_0/device/mlx4_port1_mtu
But you've answered that by "vendor specific". Thanks for the valuable
information!
For us most interesting would be if the MTU can be changed live without
any service disruption. Looks like the mlx4 driver can't provide that.
Perhaps switches can do that.
Cheers,
Sebastian
--
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:[~2013-04-09 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 11:12 tune ib stack Vasiliy Tolstov
[not found] ` <CACaajQs7RHR9Uz_M46o+1zui8x=HneQFW-09V_XQbo8OQV3eoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-09 11:43 ` Sebastian Riemer
[not found] ` <5163FEF4.1000507-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-04-09 11:51 ` Vasiliy Tolstov
[not found] ` <CACaajQva3nUe+u3YpHoE4wgiR6-mDoQtnOhR4Cpeu4iwPK0HUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-09 12:15 ` Sebastian Riemer
[not found] ` <51640654.1000009-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-04-09 13:00 ` Hal Rosenstock
2013-04-09 12:49 ` Hal Rosenstock
[not found] ` <51640E72.3010202-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-04-09 13:16 ` Sebastian Riemer
[not found] ` <516414BD.4020407-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-04-09 13:34 ` Hal Rosenstock
[not found] ` <516418F4.4040908-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-04-09 13:56 ` Sebastian Riemer
[not found] ` <51641E0D.2050009-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-04-09 14:23 ` Hal Rosenstock
[not found] ` <5164245E.2030208-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-04-09 14:37 ` Sebastian Riemer [this message]
[not found] ` <51642795.1070208-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-05-14 10:02 ` Vasiliy Tolstov
[not found] ` <CACaajQsMsZL-13aS39Asi7Z+4chXreZk5zy9QNuJM_4GcBFFBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-14 16:02 ` Sebastian Riemer
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=51642795.1070208@profitbricks.com \
--to=sebastian.riemer-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@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