<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:31:42 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-3184] link max_rpcs_in_flight to peer credits</title>
                <link>https://jira.whamcloud.com/browse/LU-3184</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;Andreas writing with James&amp;#39; account&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;The client max_rpcs_in_flight parameter is often tuned to try and get better performance from clients with large bandwidth-delay products.  Unfortunately, people are less familiar with tuning the LNET peer credits values, and this results in the Lustre layer trying to send RPCs concurrently that will never go on the wire at the same time.&lt;/p&gt;

&lt;p&gt;It would make sense to increase the LNET peer credits when the max_rpcs_in_flight is increased above the current value, so that users get the behaviour that they expect.&lt;/p&gt;</description>
                <environment></environment>
        <key id="18443">LU-3184</key>
            <summary>link max_rpcs_in_flight to peer credits</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Wed, 17 Apr 2013 18:56:33 +0000</created>
                <updated>Sun, 21 Feb 2016 22:51:22 +0000</updated>
                                            <version>Lustre 2.5.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="57287" author="isaac" created="Tue, 30 Apr 2013 02:50:53 +0000"  >&lt;p&gt;I don&apos;t think they can be linked:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;max_rpcs_in_flight is end-to-end, while LNET peer credits is not. For example, with peer credits 8 and 100 available routers, a client would be able to have at most 800 messages in flight to a server via the routers, in which case you surely don&apos;t want to limit max_rpcs_in_flight to be only 8.&lt;/li&gt;
	&lt;li&gt;when max_rpcs_in_flight is known, LNET has already initialized and the peer credits can&apos;t be changed dynamically.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="57289" author="spitzcor" created="Tue, 30 Apr 2013 03:55:37 +0000"  >&lt;p&gt;You might not be able to tie max_rpcs_in_flight to ni credits either, but it would be easier than peer_credits alone.  Maybe this just turns into an LUDOC bug where the guidance on tuning is updated then?&lt;/p&gt;

&lt;p&gt;What are your thoughts about linking (in some way, not necessarily rigidly) max_rpcs_in_flight and max_dirty_mb?&lt;/p&gt;</comment>
                            <comment id="97481" author="adilger" created="Fri, 24 Oct 2014 22:27:13 +0000"  >&lt;p&gt;If you don&apos;t think that there should be a link in the code between &lt;tt&gt;max_rpcs_in_flight&lt;/tt&gt; and peer credits/NI credits, could you please submit a patch to the Lustre User Manual to link places that discuss tuning max_rpcs_in_flight to the relevant sections that describe tuning peer credits/NI credits, and how they interact.  I still see many places where people advocate increasing max_rpcs_in_flight, but this may not help if there are not enough peer credits.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvoef:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7772</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>