From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Markus Stockhausen
<stockhausen-FhFLwxQf9jkb1SvskN2V4Q@public.gmane.org>,
Erez Shitrit
<erezsh-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"s.wendy.cheng-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<s.wendy.cheng-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Saeed Mahameed <saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: AW: AW: ACK behaviour difference LRO/GRO
Date: Wed, 30 Oct 2013 09:40:16 +0200 [thread overview]
Message-ID: <5270B7E0.5030202@mellanox.com> (raw)
In-Reply-To: <12EF8D94C6F8734FB2FF37B9FBEDD173585A214B-Xnr6BND5kcg29+KCeZIpYi5l6jQMEky5@public.gmane.org>
On 29/10/2013 23:17, Markus Stockhausen wrote:
> I would confirm that there is still room to improve GRO even in newest kernels
indeed, so there IS aggregation but the BW isn't as good as it used to
be with LRO, maybe something
in IPoIB doesn't play well with the core kernel NAPI/GRO/Interrupt
Coalescing APIs/Layers.
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-30 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 19:34 ACK behaviour difference LRO/GRO Markus Stockhausen
[not found] ` <12EF8D94C6F8734FB2FF37B9FBEDD173585A080F-Xnr6BND5kcg29+KCeZIpYi5l6jQMEky5@public.gmane.org>
2013-10-29 7:21 ` Wendy Cheng
2013-10-29 8:31 ` Or Gerlitz
[not found] ` <526F725A.1040009-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-29 11:10 ` AW: " Markus Stockhausen
[not found] ` <12EF8D94C6F8734FB2FF37B9FBEDD173585A0CFD-Xnr6BND5kcg29+KCeZIpYi5l6jQMEky5@public.gmane.org>
2013-10-29 11:43 ` Or Gerlitz
[not found] ` <526F9F5A.7010903-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-29 12:55 ` Erez Shitrit
[not found] ` <526FB051.5020709-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-10-29 13:58 ` Or Gerlitz
[not found] ` <526FBEF7.2030807-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-29 15:54 ` AW: " Markus Stockhausen
[not found] ` <12EF8D94C6F8734FB2FF37B9FBEDD173585A1FCB-Xnr6BND5kcg29+KCeZIpYi5l6jQMEky5@public.gmane.org>
2013-10-29 15:55 ` Or Gerlitz
[not found] ` <526FDA6E.3030708-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-29 21:17 ` Markus Stockhausen
[not found] ` <12EF8D94C6F8734FB2FF37B9FBEDD173585A214B-Xnr6BND5kcg29+KCeZIpYi5l6jQMEky5@public.gmane.org>
2013-10-30 7:40 ` Or Gerlitz [this message]
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=5270B7E0.5030202@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=erezsh-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s.wendy.cheng-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=stockhausen-FhFLwxQf9jkb1SvskN2V4Q@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox