From: Krishnamraju Eraparaju <krishna2@chelsio.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: faisal.latif@intel.com, shiraz.saleem@intel.com,
mkalderon@marvell.com, aelior@marvell.com, dledford@redhat.com,
jgg@ziepe.ca, linux-rdma@vger.kernel.org, bharat@chelsio.com,
nirranjan@chelsio.com
Subject: Re: [RFC PATCH] RDMA/siw: Experimental e2e negotiation of GSO usage.
Date: Wed, 15 Apr 2020 18:22:05 +0530 [thread overview]
Message-ID: <20200415125203.GA8720@chelsio.com> (raw)
In-Reply-To: <OFA289A103.141EDDE1-ON0025854B.003ED42A-0025854B.0041DBD8@notes.na.collabserv.com>
On Wednesday, April 04/15/20, 2020 at 11:59:21 +0000, Bernard Metzler wrote:
> >At present, Chelsio T6 adapter could understand upto 16KB large FPDU
> >size, max.
> >
> That's interesting and would already better the performance for
> siw <-> hardware iwarp substantially I guess. Did you try that?
Yes I see almost 3x perfromace gain when GSO is enabled.
That is, on a siw<->T6 setup, with 1500 MTU size:
GSO disabled: ~25Gbps
GSO enabled: ~72Gbps
next prev parent reply other threads:[~2020-04-15 12:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 14:48 [RFC PATCH] RDMA/siw: Experimental e2e negotiation of GSO usage Bernard Metzler
[not found] ` <20200415105135.GA8246@chelsio.com>
2020-04-15 11:59 ` Bernard Metzler
2020-04-15 12:52 ` Krishnamraju Eraparaju [this message]
2020-04-28 20:00 ` Krishnamraju Eraparaju
2020-05-05 11:19 ` Bernard Metzler
2020-05-07 11:06 ` Krishnamraju Eraparaju
2020-05-11 15:28 ` Bernard Metzler
2020-05-13 3:49 ` Krishnamraju Eraparaju
2020-05-13 11:25 ` Bernard Metzler
2020-05-14 11:17 ` Krishnamraju Eraparaju
2020-05-14 13:07 ` Bernard Metzler
2020-05-15 13:50 ` Krishnamraju Eraparaju
2020-05-15 13:58 ` Krishnamraju Eraparaju
2020-05-26 13:57 ` Bernard Metzler
2020-05-27 16:07 ` Krishnamraju Eraparaju
2020-05-31 7:03 ` Michal Kalderon
2020-05-29 15:20 ` Saleem, Shiraz
2020-05-29 15:48 ` Bernard Metzler
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=20200415125203.GA8720@chelsio.com \
--to=krishna2@chelsio.com \
--cc=BMT@zurich.ibm.com \
--cc=aelior@marvell.com \
--cc=bharat@chelsio.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=mkalderon@marvell.com \
--cc=nirranjan@chelsio.com \
--cc=shiraz.saleem@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).