<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:35:10 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-3583] LDLM support for atomic match_or_enqueue operation</title>
                <link>https://jira.whamcloud.com/browse/LU-3583</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;During inspection of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-2869&quot; title=&quot;extended attribute cache for Lustre&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-2869&quot;&gt;&lt;del&gt;LU-2869&lt;/del&gt;&lt;/a&gt; I was asked to file a ticket to track this problem in the future.&lt;/p&gt;

&lt;p&gt;The issue is that client-side LDLM does not have support for atomic match_or_enqueue operations. This may cause several lock enqueue requests being issued in parallel by a single client causing lock ping-pongs.&lt;/p&gt;

&lt;p&gt;It looks like different parts of Lustre code either ignore this problem or solve it in a specific way. For example, ll_layout_refresh() implements the atomic operation by serializing requests with lli_layout_mutex. The extended attribute cache patch uses the same technique with lli_xattrs_enq_lock().&lt;/p&gt;</description>
                <environment></environment>
        <key id="19804">LU-3583</key>
            <summary>LDLM support for atomic match_or_enqueue operation</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="panda">Andrew Perepechko</reporter>
                        <labels>
                    </labels>
                <created>Sun, 14 Jul 2013 19:14:51 +0000</created>
                <updated>Mon, 15 Jul 2013 15:28:34 +0000</updated>
                                            <version>Lustre 2.5.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="62254" author="panda" created="Sun, 14 Jul 2013 19:17:11 +0000"  >&lt;p&gt;It should probably be implemented as part of LDLM API.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="17700">LU-2869</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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|hzvvbz:</customfieldvalue>

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