<html>
    <head>
      <base href="https://bugs.dpdk.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8" class="bz_new_table">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED - l3fwd: perf reports affected by silently enabling "fast free""
   href="https://bugs.dpdk.org/show_bug.cgi?id=1231">1231</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>l3fwd: perf reports affected by silently enabling "fast free"
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DPDK
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>examples
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>dev@dpdk.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>mb@smartsharesystems.com
          </td>
        </tr>

        <tr>
          <th>Target Milestone</th>
          <td>---
          </td>
        </tr></table>
      <p>
        <div class="bz_comment_block">
          <pre class="bz_comment_text">The l3fwd example application is used for benchmarking, including the official
NIC performance reports published on the DPDK web site [1].

A patch to silently enable the "fast free" (RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE)
optimization was applied to l3fwd [2][3] in January 2018.

This means that the performance reports starting from DPDK 18.02 do not reflect
generic performance, but the performance of applications that meet the
preconditions for using this optimization feature.

In order to prevent misleading performance results, such non-generic
optimizations should be not be silently enabled; they should be explicitly
enabled using a command line option in l3fwd.

The same applies to the coming "buffer recycle" optimization.

[1]: <a href="https://core.dpdk.org/perf-reports/">https://core.dpdk.org/perf-reports/</a>
[2]: <a href="http://inbox.dpdk.org/dev/cover.1514280003.git.shahafs@mellanox.com/">http://inbox.dpdk.org/dev/cover.1514280003.git.shahafs@mellanox.com/</a>
[3]:
<a href="http://git.dpdk.org/dpdk/commit/examples/l3fwd/main.c?id=1ef9600b2d20078538ca4082f9a4adf2d9bd2ab2">http://git.dpdk.org/dpdk/commit/examples/l3fwd/main.c?id=1ef9600b2d20078538ca4082f9a4adf2d9bd2ab2</a>

PS: I don't oppose to NIC vendors publishing performance results using
non-generic optimizations such as "fast free" or the coming "buffer recycle",
but it should be fully disclosed which optimizations have been used to achieve
better results.
          </pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
      <div itemscope itemtype="http://schema.org/EmailMessage">
        <div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
          
          <link itemprop="url" href="https://bugs.dpdk.org/show_bug.cgi?id=1231">
          <meta itemprop="name" content="View bug">
        </div>
        <meta itemprop="description" content="Bugzilla bug update notification">
      </div>
    </body>
</html>