From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Event ring is full when do iozone test on UAS storage
Date: Mon, 16 Sep 2019 16:42:18 +0300 [thread overview]
Message-ID: <0aae13f2-04cf-f45a-e6ee-4bf9e515faba@linux.intel.com> (raw)
In-Reply-To: <20190916094305.GB21844@b29397-desktop>
On 16.9.2019 12.41, Peter Chen wrote:
> Hi Mathias,
>
> I met "event ring full error" like below, this error is met when
> I do iozone test on UAS storage at v4.19.35 kernel, but not meet
> this error at linux-next tree (08/24). The same host and test
> UAS storage device are used. This issue is due to xhci_handle_event
> does not return 0 long time, maybe the xHC speed is fast enough
> at that time. If I force the xhci_handle_event only run 100 times
> before update ERST dequene pointer, it will not occur this error.
> I did not see any changes for xhci_handle_event at the latest code,
> so in theory, it should have this issue too. Do you think if we need
> to improve xhci_handle_event to avoid event ring?
Possibly.
We need to check the details of what types of events the
ring is filled with, and why handling them takes so long.
does irqsoff tracing show anything blocking interrupts for long?
It's also possible that we don't get interrupts early enough.
Either if interupts are moderated, or event ring is filled with events that
don't generate interrupts (BEI flag set).
-Mathias
next parent reply other threads:[~2019-09-16 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190916094305.GB21844@b29397-desktop>
2019-09-16 13:42 ` Mathias Nyman [this message]
[not found] ` <CAL411-oirjSLZzwoN8axqpfn-JQ8eEGMWD-w9p24Krap+dPs9g@mail.gmail.com>
2019-09-18 14:38 ` Event ring is full when do iozone test on UAS storage Mathias Nyman
2019-09-19 9:54 ` Peter Chen
2019-09-19 13:59 ` Suwan Kim
2019-09-23 11:19 ` Mathias Nyman
2019-09-23 13:46 ` Mathias Nyman
2019-09-24 8:43 ` Peter Chen
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=0aae13f2-04cf-f45a-e6ee-4bf9e515faba@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.