On Tue, 2017-04-11 at 09:05 -0700, Eric Dumazet wrote: > Some kind of copybreak maybe ? > > perf record -a -g sleep 5 > perf report --stdio > > Copybreak is generally not really useful, and can have downsides. > > Much better to let upper stacks deciding this. > > For example, there is no point doing copy break for TCP ACK packets that > are going to be consumed immediately. > > There is also no point doing copy break in case the packet will be > dropped (say by ... XDP ;) )
Yes : #define BNXT_RX_COPY_THRESH 256 For optimal results, you probably want to remove copybreak.
