<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:18:15 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-1622] hash MEs on wildcard portal when it&apos;s possible</title>
                <link>https://jira.whamcloud.com/browse/LU-1622</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In current LNet, MEs on unique portal are hashed into different lists, MEs on wildcard portal are all attached on a single list. This is fine for most use cases, but there is also requirement that user only use one portal for different request types, buffers for different request types are identified by match-bits, LNet selftest is one of this use-case because both ping and BRW tests share SRPC_REQUEST_PORTAL.&lt;br/&gt;
This is normally fine, but it could be a performance issue on server side, for example: if we created a session with bot BRW test and PING test, and we posted a thousand buffers for BRW request, 10 bufferes for PING request, if all these buffers are attached on the single list, searching for PING buffer would be very expensive.&lt;/p&gt;

&lt;p&gt;This can be fixed by hashing MEs on wildcard portal too, but we can&apos;t do this for those MEs with &quot;ignore bits&quot; because incoming message will have no idea how to hash their match information w/o knowing &quot;ignore bits&quot; of sink buffer. So we should still attach all MEs with ignore bits on the single list, and always check this list first, no matter it&apos;s wildcard portal or unique portal.&lt;/p&gt;

&lt;p&gt;This means if user mixed MEs with &quot;ignore bits&quot; and w/o &quot;ignore bits&quot; on one portal or set &quot;ignore bits&quot; for MEs on unique portal, there still could be performance issue, but they should be deprecated, and we don&apos;t have such use-case.&lt;/p&gt;</description>
                <environment></environment>
        <key id="15192">LU-1622</key>
            <summary>hash MEs on wildcard portal when it&apos;s possible</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="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="liang">Liang Zhen</assignee>
                                    <reporter username="liang">Liang Zhen</reporter>
                        <labels>
                    </labels>
                <created>Wed, 11 Jul 2012 11:37:12 +0000</created>
                <updated>Tue, 8 Jan 2013 18:34:42 +0000</updated>
                            <resolved>Tue, 28 Aug 2012 12:17:00 +0000</resolved>
                                    <version>Lustre 2.3.0</version>
                                    <fixVersion>Lustre 2.3.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="41711" author="liang" created="Wed, 11 Jul 2012 13:33:24 +0000"  >&lt;p&gt;Patch is here &lt;a href=&quot;http://review.whamcloud.com/3376&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/3376&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="41783" author="liang" created="Fri, 13 Jul 2012 04:28:14 +0000"  >&lt;p&gt;We also need to take care of enabled/disabled status of match-table in this patch, so it&apos;s a little more complex than I think, will update it soon.&lt;/p&gt;</comment>
                            <comment id="41904" author="spitzcor" created="Mon, 16 Jul 2012 16:00:21 +0000"  >&lt;p&gt;Liang, are you looking at expanding lnet-selftest.sh to demonstrate?  Or, are you just using the existing acc-sm test?&lt;/p&gt;</comment>
                            <comment id="41922" author="liang" created="Tue, 17 Jul 2012 04:30:16 +0000"  >&lt;p&gt;No, I will use my own scripts, selftest is part of demonstration because it can only demonstrate LNet performance, we will also use mdtest to show performance of the whole server stack.&lt;/p&gt;</comment>
                            <comment id="43885" author="liang" created="Tue, 28 Aug 2012 12:17:00 +0000"  >&lt;p&gt;Patch landed&lt;/p&gt;</comment>
                            <comment id="50172" author="wang" created="Tue, 8 Jan 2013 18:34:42 +0000"  >&lt;p&gt;Cray&apos;s DVS does have a use case that mixes MEs with &quot;ignore bits&quot; and w/o &quot;ignore bits&quot; on one portal. The ignore bits is used as &apos;catch all&apos; for spurious messages if ME bits not matching. DVS will temporarily fix it by making all MEs with ignore bits so that they all are on one list. But DVS does prefer to have hashed ME lists for performance. Please consider this use case for current testing and future design.&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|hzv67b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4539</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>