<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>c1e7e466 - IB/mlx4: Add iov directory in sysfs under the ib device</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#c1e7e466</link>
        <description>IB/mlx4: Add iov directory in sysfs under the ib deviceThis directory is added only for the master -- slaves do not have it.The sysfs iov directory is used to manage and examine the port P_Keyand guid paravirtualization.Under iov/ports, the administrator may examine the gid and P_Key tablesas they are present in the device (and as are seen in the &quot;networkview&quot; presented to the SM).Under the iov/&lt;pci slot number&gt; directories, the admin may map theindex numbers in the physical tables (as under iov/ports) to theparavirtualized index numbers that guests see.For example, if the administrator, for port 1 on guest 2 maps physicalpkey index 10 to virtual index 1, then that guest, whenever it usesits pkey index 1, will actually be using the real pkey index 10.Based on patch from Erez Shitrit &lt;erezsh@mellanox.com&gt;Signed-off-by: Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;Signed-off-by: Roland Dreier &lt;roland@purestorage.com&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Fri, 03 Aug 2012 08:40:51 +0000</pubDate>
        <dc:creator>Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;</dc:creator>
    </item>
<item>
        <title>a0c64a17 - mlx4: Add alias_guid mechanism</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#a0c64a17</link>
        <description>mlx4: Add alias_guid mechanismFor IB ports, we paravirtualize the GUID at index 0 on slaves.  TheGUID at index 0 seen by a slave is the actual GUID occupying the GUIDtable at the slave-id index.The driver, by default, requests at startup time that subnet managerpopulate its entire guid table with GUIDs. These guids are then mapped(paravirtualized) to the slaves, and appear for each slave as its GUIDat index 0.Until each slave has such a guid, its port status is DOWN.The guid table is cached to support special QP paravirtualization, andevent propagation to slaves on guid change (we test to see if the guidreally changed before propagating an event to the slave).To support this caching, add capability to __mlx4_ib_query_gid() toobtain the network view (i.e., physical view) gid at index X, not justthe host (paravirtualized) view.Based on a patch from Erez Shitrit &lt;erezsh@mellanox.com&gt;Signed-off-by: Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;Signed-off-by: Roland Dreier &lt;roland@purestorage.com&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Fri, 03 Aug 2012 08:40:49 +0000</pubDate>
        <dc:creator>Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;</dc:creator>
    </item>
<item>
        <title>3cf69cc8 - IB/mlx4: Add CM paravirtualization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#3cf69cc8</link>
        <description>IB/mlx4: Add CM paravirtualizationIn CM para-virtualization:1. Incoming requests are steered to the correct vHCA according to the   embedded GID.2. Communication IDs on outgoing requests are replaced by a globally   unique ID, generated by the PPF, since there is no synchronization   of ID generation between guests (and so these IDs are not   guaranteed to be globally unique).  The guest&apos;s comm ID is stored,   and is returned to the response MAD when it arrives.Signed-off-by: Amir Vadai &lt;amirv@mellanox.co.il&gt;Signed-off-by: Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;Signed-off-by: Roland Dreier &lt;roland@purestorage.com&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Fri, 03 Aug 2012 08:40:47 +0000</pubDate>
        <dc:creator>Amir Vadai &lt;amirv@mellanox.co.il&gt;</dc:creator>
    </item>
<item>
        <title>b9c5d6a6 - IB/mlx4: Add multicast group (MCG) paravirtualization for SR-IOV</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#b9c5d6a6</link>
        <description>IB/mlx4: Add multicast group (MCG) paravirtualization for SR-IOVMCG paravirtualization support includes:- Creating multicast groups by VFs, and keeping accounting of them- Leaving multicast groups by VFs- Updating SM only with real changes in the overall picture of MCGs status- Creation of MGID=0 groups (let SM choose MGID)Note that the MCG module maintains its own internal MCG objectreference counts.  The reason for this is that the IB core is used totrack only the multicast groups joins generated by the PF it runsover.  The PF IB core layer is unaware of slaves, so it cannot be usedto keep track of MCG joins they generate.Signed-off-by: Oren Duer &lt;oren@mellanox.co.il&gt;Signed-off-by: Eli Cohen &lt;eli@mellanox.com&gt;Signed-off-by: Jack Morgenstein &lt;jackm@dev.mellanox.co.il&gt;Signed-off-by: Roland Dreier &lt;roland@purestorage.com&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Fri, 03 Aug 2012 08:40:46 +0000</pubDate>
        <dc:creator>Oren Duer &lt;oren@mellanox.co.il&gt;</dc:creator>
    </item>
<item>
        <title>225c7b1f - IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adapters</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/infiniband/hw/mlx4/Makefile#225c7b1f</link>
        <description>IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adaptersAdd an InfiniBand driver for Mellanox ConnectX adapters.  Becausethese adapters can also be used as ethernet NICs and Fibre Channel HBAs, the driver is split into two modules:    mlx4_core: Handles low-level things like device initialization and     processing firmware commands.  Also controls resource allocation     so that the InfiniBand, ethernet and FC functions can share a     device without stepping on each other.    mlx4_ib: Handles InfiniBand-specific things; plugs into the     InfiniBand midlayer. Signed-off-by: Roland Dreier &lt;rolandd@cisco.com&gt;

            List of files:
            /linux-6.15/drivers/infiniband/hw/mlx4/Makefile</description>
        <pubDate>Wed, 09 May 2007 01:00:38 +0000</pubDate>
        <dc:creator>Roland Dreier &lt;rolandd@cisco.com&gt;</dc:creator>
    </item>
</channel>
</rss>
