From: Sarah Newman <sarah.newman@computer.org>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: e1000-devel@lists.sf.net, Netdev <netdev@vger.kernel.org>
Subject: Re: [E1000-devel] Questions about crashes and GRO
Date: Mon, 20 Nov 2017 15:35:14 -0800 [thread overview]
Message-ID: <a200c09a-ec13-9463-82a3-e0fb7e5140ba@computer.org> (raw)
In-Reply-To: <CAKgT0Udps5K1Eu6vmsEW1ABnYOK3DgTR1bTGBMuTh5nsiQgZ3g@mail.gmail.com>
On 11/20/2017 02:56 PM, Alexander Duyck wrote:
> On Mon, Nov 20, 2017 at 2:38 PM, Sarah Newman <sarah.newman@computer.org> wrote:
>> On 11/20/2017 08:36 AM, Alexander Duyck wrote:
>>> Hi Sarah,
>>>
>>> I am adding the netdev mailing list as I am not certain this is an
>>> i350 specific issue. The traces themselves aren't anything I recognize
>>> as an existing issue. From what I can tell it looks like you are
>>> running Xen, so would I be correct in assuming you are bridging
>>> between VMs? If so are you using any sort of tunnels on your network,
>>> if so what type? This information would be useful as we may be looking
>>> at a bug in a tunnel offload for GRO.
>>
>> Yes, there's bridging. The traffic on the physical device is tagged with vlans and the bridges use untagged traffic. There are no tunnels. I do not
>> own the VMs traffic.
>>
>> Because I have only seen this on a single server with unique hardware, I think it's most likely related to the hardware or to a particular VM on that
>> server.
>
> So I would suspect traffic coming from the VM if anything. The i350 is
> a pretty common device. If we were seeing issues specific to it > would expect we would have more reports than just the one so far.
My confusion was primarily related to the release notes for an older version of a different intel driver.
But regarding traffic coming from a VM, the backtraces both include igb_poll. Doesn't that mean the problem is related to inbound traffic on the igb
device and not traffic direct from a local VM?
--Sarah
next prev parent reply other threads:[~2017-11-20 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b905cfcc-fdf3-67a0-98f4-a1560c6fd25b@computer.org>
2017-11-20 16:36 ` [E1000-devel] Questions about crashes and GRO Alexander Duyck
2017-11-20 22:38 ` Sarah Newman
2017-11-20 22:56 ` Alexander Duyck
2017-11-20 23:35 ` Sarah Newman [this message]
2017-11-21 0:04 ` Alexander Duyck
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=a200c09a-ec13-9463-82a3-e0fb7e5140ba@computer.org \
--to=sarah.newman@computer.org \
--cc=alexander.duyck@gmail.com \
--cc=e1000-devel@lists.sf.net \
--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