From: "Íñigo Huguet" <ihuguet@redhat.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>,
"Edward Cree" <ecree.xilinx@gmail.com>,
netdev@vger.kernel.org, "Dinan Gunawardena" <dinang@xilinx.com>
Subject: Re: Bad performance in RX with sfc 40G
Date: Thu, 9 Dec 2021 13:06:45 +0100 [thread overview]
Message-ID: <CACT4oufpvQ1Qzg3eC6wDu33_xBo5tVghr9G7Q=d-7F=bZbW4Vg@mail.gmail.com> (raw)
In-Reply-To: <20211120083107.z2cm7tkl2rsri2v7@gmail.com>
Hi,
On Sat, Nov 20, 2021 at 9:31 AM Martin Habets <habetsm.xilinx@gmail.com> wrote:
> If you're testing without the IOMMU enabled I suspect the recycle ring
> size may be too small. Can your try the patch below?
Sorry for the very late reply, but I've had to be out of work for many days.
This patch has improved the performance a lot, reaching the same
30Gbps than in TX. However, it seems sometimes a bit erratic, still
dropping to 15Gbps sometimes, specially after module remove & probe,
or from one iperf call to another. But not being all the times, I
didn't found a clear pattern. Anyway, it clearly improves things.
Can this patch be applied as is or it's just a test?
--
Íñigo Huguet
next prev parent reply other threads:[~2021-12-09 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 15:14 Bad performance in RX with sfc 40G Íñigo Huguet
2021-11-18 17:19 ` Eric Dumazet
2021-12-02 14:26 ` Íñigo Huguet
2021-11-20 8:31 ` Martin Habets
2021-12-09 12:06 ` Íñigo Huguet [this message]
2021-12-23 13:18 ` Íñigo Huguet
2022-01-02 9:22 ` Martin Habets
2022-01-10 8:58 ` [PATCH net-next] sfc: The size of the RX recycle ring should be more flexible Martin Habets
2022-01-10 9:31 ` Íñigo Huguet
2022-01-12 9:05 ` Martin Habets
2022-01-31 11:08 ` Martin Habets
2022-01-10 17:22 ` Jakub Kicinski
2022-01-12 9:08 ` Martin Habets
2022-01-31 11:10 ` [PATCH V2 " Martin Habets
2022-02-02 5:10 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACT4oufpvQ1Qzg3eC6wDu33_xBo5tVghr9G7Q=d-7F=bZbW4Vg@mail.gmail.com' \
--to=ihuguet@redhat.com \
--cc=dinang@xilinx.com \
--cc=ecree.xilinx@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.