<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in gro_lib.py</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a57ddd89900480dc90fd9f553f7f71a8e875bf67 - selftests: drv-net: Check the features set by set_ethtool_feat()</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/drivers/net/gro_lib.py#a57ddd89900480dc90fd9f553f7f71a8e875bf67</link>
        <description>selftests: drv-net: Check the features set by set_ethtool_feat()Read back the features after running ethtool -K to check if they wereactually applied. The drivers might refuse to set a feature silently andthe test could run with a different configuration than the requested one.Add a &apos;check&apos; parameter to skip this, as the GRO &quot;hw&quot; mode handles thecase where HW GRO is cleared by the driver.Signed-off-by: Ovidiu Panait &lt;ovidiu.panait.rb@renesas.com&gt;Reviewed-by: Nicolai Buchwitz &lt;nb@tipi-net.de&gt;Link: https://patch.msgid.link/20260918112529.96039-3-ovidiu.panait.rb@renesas.comSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/drivers/net/gro_lib.py</description>
        <pubDate>Fri, 18 Sep 2026 13:25:28 +0200</pubDate>
        <dc:creator>Ovidiu Panait &lt;ovidiu.panait.rb@renesas.com&gt;</dc:creator>
    </item>
<item>
        <title>d3630df401a8ee91117db26b14a64520aa44fbdb - selftests: drv-net: Move _set_ethtool_feat() into lib</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/drivers/net/gro_lib.py#d3630df401a8ee91117db26b14a64520aa44fbdb</link>
        <description>selftests: drv-net: Move _set_ethtool_feat() into libMove the _set_ethtool_feat() helper from gro_lib.py into lib, so that itcan be reused by the VLAN test added in the next commit. Drop the leadingunderscore, now that the helper is exported.Signed-off-by: Ovidiu Panait &lt;ovidiu.panait.rb@renesas.com&gt;Reviewed-by: Nicolai Buchwitz &lt;nb@tipi-net.de&gt;Link: https://patch.msgid.link/20260918112529.96039-2-ovidiu.panait.rb@renesas.comSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/drivers/net/gro_lib.py</description>
        <pubDate>Fri, 18 Sep 2026 13:25:27 +0200</pubDate>
        <dc:creator>Ovidiu Panait &lt;ovidiu.panait.rb@renesas.com&gt;</dc:creator>
    </item>
<item>
        <title>9a483b60a0ad67fbd55c23a0ebb96754e984f585 - selftests: drv-net: add BIG TCP test cases</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/drivers/net/gro_lib.py#9a483b60a0ad67fbd55c23a0ebb96754e984f585</link>
        <description>selftests: drv-net: add BIG TCP test casesAdd four new test cases that validate coalescingunder increased size limits (BIG TCP):big_tcp_data_same  - validates that equal-sized segments coalesce past   the legacy IP_MAXPACKET limit.big_tcp_data_lrg_sml  - validates that a smaller final segment coalesces into the    previous chain of large-sized segments while crossing the    IP_MAXPACKET limit.big_tcp_tcp_seq  - validates that a packet with a wrong sequence number doesn&apos;t    coalesce. The test uses a sequence number for which the low 16 bits    correspond to the correct sequence number to validate against    truncation bugs, since total aggregate length crosses over the    legacy size limit for BIG TCP.big_tcp_large_max  - validates that coalescing stops at the configured BIG TCP limit.Use a gro_flush_timeout value 2x higher for the BIG TCP test casesto prevent under-coalescing.Signed-off-by: Narcisa Vasile &lt;narcisav.kernel@gmail.com&gt;Link: https://patch.msgid.link/20260913052419.77910-1-narcisav.kernel@gmail.comSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/drivers/net/gro_lib.py</description>
        <pubDate>Sun, 13 Sep 2026 07:24:19 +0200</pubDate>
        <dc:creator>Narcisa Vasile &lt;narcisav.kernel@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>348ea4642f56ab3dc93621c8e3ab0ccd0e5f1782 - selftests: net: add ctl_file_write() helper</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/drivers/net/gro_lib.py#348ea4642f56ab3dc93621c8e3ab0ccd0e5f1782</link>
        <description>selftests: net: add ctl_file_write() helperSetting a sysctl or a sysfs attribute for the duration of a test andputting the old value back has been open coded multiple times.We generally avoid creating library helpers but this one is verycommon, and the defer is a little tricky as using the same functionfor defer as the initial write leads to an infinite loop (not thatI would ever make such mistake!)Some of the conversions are not identical, but arguably ctl_file_write()semantics are more correct.Reviewed-by: Nimrod Oren &lt;noren@nvidia.com&gt;Reviewed-by: Bobby Eshleman &lt;bobbyeshleman@meta.com&gt;Link: https://patch.msgid.link/20260909180009.1894019-1-kuba@kernel.orgSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/drivers/net/gro_lib.py</description>
        <pubDate>Wed, 09 Sep 2026 20:00:09 +0200</pubDate>
        <dc:creator>Jakub Kicinski &lt;kuba@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f225a7317c18f2009fb4cdcc75337c726b6dda88 - selftests: drv-net: split gro.py into one test per coalescing mode</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/drivers/net/gro_lib.py#f225a7317c18f2009fb4cdcc75337c726b6dda88</link>
        <description>selftests: drv-net: split gro.py into one test per coalescing modegro.py runs its full set of cases three times over - against SW GRO,HW GRO and LRO. It&apos;s our test with the longest runtime. The 318 casestake 12m30s on mlx5 with a debug kernel.Bumping the timeout for all tests feels wrong when we can so easilysplit the GRO test by execution mode. Shorter runtime also helps retryjust the failing portion / mode (we retry failing tests to try todetect flakes vs real failures).Move the main logic to gro_lib.py and add one program per mode -gro_sw.py, gro_hw.py and gro_lro.py, 102 cases each. Move PPPoE toa dedicated test. It has been tacked onto the tests in an ugly way,and it only runs against SW GRO anyway.Note that unfortunately this will case a rename of all test cases.The mode moves from the case name to the test name  gro.py test.sw_ipv4_data_samebecomes  gro_sw.py test.ipv4_data_sameReviewed-by: Joe Damato &lt;joe@dama.to&gt;Reviewed-by: Nimrod Oren &lt;noren@nvidia.com&gt;Reviewed-by: Willem de Bruijn &lt;willemb@google.com&gt;Link: https://patch.msgid.link/20260901200728.2063720-3-kuba@kernel.orgSigned-off-by: Jakub Kicinski &lt;kuba@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/drivers/net/gro_lib.py</description>
        <pubDate>Tue, 01 Sep 2026 22:07:27 +0200</pubDate>
        <dc:creator>Jakub Kicinski &lt;kuba@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
