From: Jan.Glauber@cavium.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA remote memcpy requests
Date: Fri, 12 Oct 2018 11:03:34 +0000 [thread overview]
Message-ID: <20181012110326.GA6721@hc> (raw)
In-Reply-To: <DM6PR04MB4059742D494D96FC11674A50F2E20@DM6PR04MB4059.namprd04.prod.outlook.com>
On Fri, Oct 12, 2018 at 09:48:01AM +0000, Adam Cottrel wrote:
> Hi Will,
>
> Thank you for getting back to me.
>
> > [+Robin and Cavium folks -- it's usually best to cc people as well as mailing
> > the list]
> I will remember this for future. Thanks for the advice.
>
> > > I am using the ATH10K on Linux 14.4 with an Arm Cavium processor.
> > > During heavy loading, I am seeing that target initiated DMA requests
> > > are being silently dropped under extreme IO memory pressure and it is
> > > proving very difficult to isolate the root cause.
> >
> > Is this ThunderX 1 or 2 or something else? Can you reproduce the issue with
> > mainline?
> I am using:-
> model = "Cavium ThunderX CN81XX board";
> compatible = "cavium,thunder-81xx";
>
Hi Adam,
what is the exact hardware revision (shown in /proc/cpuinfo) ?
--Jan
next prev parent reply other threads:[~2018-10-12 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 7:28 DMA remote memcpy requests Adam Cottrel
2018-10-12 9:09 ` Will Deacon
2018-10-12 9:48 ` Adam Cottrel
2018-10-12 10:46 ` Robin Murphy
2018-10-12 11:06 ` Adam Cottrel
2018-10-15 14:34 ` Adam Cottrel
2018-10-15 15:09 ` Jan Glauber
2018-10-15 15:24 ` Adam Cottrel
2018-10-15 15:39 ` Jan Glauber
2018-10-15 15:51 ` Adam Cottrel
2018-10-18 15:36 ` Adam Cottrel
2018-10-22 14:28 ` Jan Glauber
2018-10-22 14:39 ` Adam Cottrel
2018-10-22 15:33 ` Jan Glauber
[not found] ` <DM6PR07MB4923F3328079199090D6D2CA9EFE0@DM6PR07MB4923.namprd07.prod.outlook.com>
2018-10-16 16:52 ` Adam Cottrel
2018-10-16 17:08 ` Robin Murphy
2018-10-12 11:03 ` Jan Glauber [this message]
2018-10-12 11:07 ` Adam Cottrel
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=20181012110326.GA6721@hc \
--to=jan.glauber@cavium.com \
--cc=linux-arm-kernel@lists.infradead.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).