netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Wilder <dwilder@us.ibm.com>
To: netdev@vger.kernel.org
Cc: tlfalcon@linux.ibm.com, cris.forno@ibm.com,
	pradeeps@linux.vnet.ibm.com, wilder@us.ibm.com,
	willemdebruijn.kernel@gmail.com, kuba@kernel.org
Subject: [ PATCH v2 0/2] ibmveth gso fix.
Date: Tue, 13 Oct 2020 16:20:12 -0700	[thread overview]
Message-ID: <20201013232014.26044-1-dwilder@us.ibm.com> (raw)

The ibmveth driver is a virtual Ethernet driver used on IBM pSeries systems.
Gso packets can be sent between LPARS (virtual hosts) without segmentation,
by flagging gso packets using one of two methods depending on the firmware
version. Some gso packet were not correctly identified by the receiver.
This patch-set corrects this issue.

V2:
- Added fix tags.
- Byteswap the constant at compilation time.
- Updated the commit message to clarify what frame validation is performed
  by the hypervisor.

Signed-off-by: David Wilder <dwilder@us.ibm.com>
Reviewed-by: Thomas Falcon <tlfalcon@linux.ibm.com>
Reviewed-by: Cristobal Forno <cris.forno@ibm.com>
Reviewed-by: Pradeep Satyanarayana <pradeeps@linux.vnet.ibm.com>

David Wilder (2):
  ibmveth: Switch order of ibmveth_helper calls.
  ibmveth: Identify ingress large send packets.

 drivers/net/ethernet/ibm/ibmveth.c | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-10-13 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 23:20 David Wilder [this message]
2020-10-13 23:20 ` [ PATCH v2 1/2] ibmveth: Switch order of ibmveth_helper calls David Wilder
2020-10-14 16:22   ` Willem de Bruijn
2020-10-15  3:23   ` Jakub Kicinski
2020-10-13 23:20 ` [ PATCH v2 2/2] ibmveth: Identify ingress large send packets David Wilder
2020-10-14 16:23   ` Willem de Bruijn
2020-10-15  3:23 ` [ PATCH v2 0/2] ibmveth gso fix Jakub Kicinski

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=20201013232014.26044-1-dwilder@us.ibm.com \
    --to=dwilder@us.ibm.com \
    --cc=cris.forno@ibm.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pradeeps@linux.vnet.ibm.com \
    --cc=tlfalcon@linux.ibm.com \
    --cc=wilder@us.ibm.com \
    --cc=willemdebruijn.kernel@gmail.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).