From: Simon Huelck <simonmail@gmx.de>
To: Jose Abreu <jose.abreu@synopsys.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Emiliano Ingrassia <ingrassia@epigenesys.com>,
Gpeppe.cavallaro@st.com, alexandre.torgue@st.com,
linux-amlogic@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: stmmac / meson8b-dwmac
Date: Mon, 18 Feb 2019 13:33:42 +0100 [thread overview]
Message-ID: <7afdaa0d-d0ef-b223-1f6e-2b52bfa44784@gmx.de> (raw)
In-Reply-To: <c80c1e5b-fed9-25ce-eb1b-258ac0135ce7@synopsys.com>
Hi,
i recognize the followin on my ethernet stats:
threshold: 1
tx_pkt_n: 1457325
rx_pkt_n: 5022405
normal_irq_n: 671738
rx_normal_irq_n: 606573
napi_poll: 784439
tx_normal_irq_n: 61061
tx_clean: 784439
tx_set_ic_bit: 58293
irq_receive_pmt_irq_n: 0
mmc_tx_irq_n: 0
mmc_rx_irq_n: 0
mmc_rx_csum_offload_irq_n: 0
-> irq_tx_path_in_lpi_mode_n: 382037
-> irq_tx_path_exit_lpi_mode_n: 382021
Is this normal ?
regards,
Simon
Am 18.02.2019 um 09:45 schrieb Jose Abreu:
> On 2/18/2019 8:42 AM, Jose Abreu wrote:
>> On 2/17/2019 2:48 PM, Martin Blumenstingl wrote:
>>> Jose, is my command for disabling offloading correct?
>> Yes, I think so. What about NIC statistics and logs ? ("ethtool
>> -S eth0", "dmesg | grep -i stmmac")
> And, "ifconfig eth0" after running the test.
>
>> Thanks,
>> Jose Miguel Abreu
>>
next prev parent reply other threads:[~2019-02-18 12:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a38e643c-ed9f-c306-cc95-84f70ebc1f10@gmx.de>
[not found] ` <CAFBinCDebPOsmrhSXecx48nGWHh7g_OGPbr1Y0M+n_v9Ht91ew@mail.gmail.com>
2019-01-17 21:23 ` stmmac / meson8b-dwmac Simon Huelck
2019-02-04 14:34 ` Martin Blumenstingl
2019-02-06 10:36 ` Emiliano Ingrassia
2019-02-06 18:04 ` Simon Huelck
2019-02-06 21:21 ` Simon Huelck
2019-02-07 19:30 ` Simon Huelck
2019-02-09 1:09 ` Martin Blumenstingl
2019-02-11 13:44 ` Jose Abreu
2019-02-14 7:21 ` Simon Huelck
2019-02-17 14:48 ` Martin Blumenstingl
2019-02-17 19:13 ` Simon Huelck
2019-02-18 8:42 ` Jose Abreu
2019-02-18 8:45 ` Jose Abreu
2019-02-18 12:33 ` Simon Huelck [this message]
2019-02-18 12:41 ` Jose Abreu
2019-02-18 13:02 ` Jose Abreu
2019-02-18 15:29 ` Simon Huelck
2019-02-18 15:31 ` Jose Abreu
2019-02-18 15:53 ` Simon Huelck
2019-02-18 16:26 ` Jose Abreu
2019-02-18 16:40 ` Simon Huelck
2019-02-18 16:43 ` Jose Abreu
2019-02-18 16:51 ` Simon Huelck
2019-02-18 17:05 ` Jose Abreu
2019-02-18 18:05 ` Simon Huelck
2019-02-19 8:47 ` Jose Abreu
2019-02-19 19:41 ` Simon Huelck
2019-02-21 14:21 ` Jerome Brunet
2019-02-21 17:27 ` Simon Huelck
2019-02-21 17:46 ` Jerome Brunet
2019-02-21 19:34 ` Simon Huelck
2019-02-22 17:21 ` Anand Moon
2019-02-24 15:00 ` Simon Huelck
2019-02-24 15:02 ` Simon Huelck
2019-02-24 19:42 ` Sebastian Gottschall
2019-02-24 20:34 ` Simon Huelck
2019-02-27 11:09 ` Jose Abreu
2019-02-27 19:02 ` Simon Huelck
2019-03-01 9:23 ` Jose Abreu
2019-03-05 9:55 ` Simon Huelck
2019-03-06 11:35 ` Simon Huelck
2019-03-06 11:45 ` Simon Huelck
2019-05-11 14:53 ` Simon Huelck
2019-05-13 9:07 ` Jose Abreu
2019-05-22 12:48 ` Simon Huelck
2019-05-22 14:02 ` Neil Armstrong
2019-02-27 21:03 ` Simon Huelck
2019-02-18 17:05 ` Simon Huelck
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=7afdaa0d-d0ef-b223-1f6e-2b52bfa44784@gmx.de \
--to=simonmail@gmx.de \
--cc=Gpeppe.cavallaro@st.com \
--cc=alexandre.torgue@st.com \
--cc=ingrassia@epigenesys.com \
--cc=jose.abreu@synopsys.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.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).