netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Alexander Duyck <aduyck@mirantis.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	jesse.brandeburg@intel.com, alexander.duyck@gmail.com,
	jeffrey.t.kirsher@intel.com
Subject: Re: [net PATCH] i40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per packet
Date: Wed, 30 Mar 2016 13:00:11 -0400	[thread overview]
Message-ID: <20160330170011.GB27540@oracle.com> (raw)
In-Reply-To: <20160330064213.12927.46852.stgit@localhost.localdomain>

On (03/29/16 23:44), Alexander Duyck wrote:
> This patch has been sanity checked only.  I cannot yet guarantee it
> resolves the original issue that was reported.  I'll try to get a
> reproduction environment setup tomorrow but I don't know how long that
> should take.

I tried this out with rds-stress on my test-pair, unfortunately, I
still see the Tx hang.

Setting up the test is quite easy- for reference, the instructions 
are here:
   https://sourceforge.net/p/e1000/mailman/message/34936766/

--Sowmini

  reply	other threads:[~2016-03-30 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  6:44 [net PATCH] i40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per packet Alexander Duyck
2016-03-30 17:00 ` Sowmini Varadhan [this message]
2016-03-30 17:12   ` Alexander Duyck
2016-03-30 17:20     ` Sowmini Varadhan
2016-03-30 17:35       ` Alexander Duyck
2016-03-30 19:41         ` Jesse Brandeburg
2016-03-30 20:09           ` Sowmini Varadhan
2016-03-30 20:15             ` Eric Dumazet
2016-03-30 20:40               ` Sowmini Varadhan
2016-03-30 21:20           ` Alexander Duyck
2016-03-30 23:06             ` Alexander Duyck
2016-03-30 18:38     ` Jesse Brandeburg

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=20160330170011.GB27540@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=aduyck@mirantis.com \
    --cc=alexander.duyck@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.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 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).