xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Steve Prochniak <steve.prochniak@oracle.com>
To: Konrad Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Pls help: netfront tx ring frozen (any clues appreciated)
Date: Mon, 9 Apr 2012 12:09:19 -0700 (PDT)	[thread overview]
Message-ID: <7df0d150-21e5-48ba-b3a4-41ae7e45b4f7@default> (raw)
In-Reply-To: <20120406203152.GB15674@phenom.dumpdata.com>

I recall running into this problem while in development for a Network PV driver - though I don't recall if it was the TX or RX ring that would stall (maybe it was both or either).  During longevity testing, after days of nonstop traffic, something would go wrong and the interrupt would fail to clear.  This seemed to be a "after so many interrupts" bug, since halving the traffic would double the time necessary to reproduce.  At the time, we figured that we never saw this with the disk because it would have taken weeks to repro.

Mainly because of the length of time required to reproduce this, we never found out whether the problem was on the Dom0 or DomU side.  I worked around the problem by adding code that would detect that the condition was occurring, and then would trigger a reset of the event channel or interrupt.

Steve

-----Original Message-----
From: Konrad Rzeszutek Wilk 
Sent: Friday, April 06, 2012 4:32 PM
To: Vijay Chander
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Pls help: netfront tx ring frozen (any clues appreciated)

On Sat, Feb 25, 2012 at 07:46:36AM -0800, Vijay Chander wrote:
> If anybody encountered a similar situation as below where the netfront TX
> ring is stuck ,
> can you pls provide some pointers on how to get around this problem ?
> 
> This typically happens after about 2days of overnight traffic tests.

What kind of traffic? As in netperf for 48hrs? Is this from guest to guest
traffic or from outside host to the guest?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-04-09 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJNqtuqZo5VKvGtYnGxp543dQ1FNk2Lz-8jzt5QnDYjR+XiS6w@mail.gmail.com>
2012-02-23 16:29 ` Pls help: netfront tx ring frozen (any clues appreciated) Vijay Chander
2012-02-25 15:46   ` Vijay Chander
2012-04-06 20:31     ` Konrad Rzeszutek Wilk
2012-04-09 19:09       ` Steve Prochniak [this message]
2012-04-09 19:21         ` Steve Prochniak

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=7df0d150-21e5-48ba-b3a4-41ae7e45b4f7@default \
    --to=steve.prochniak@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.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).