From: David Miller <davem@davemloft.net>
To: Jose.Abreu@synopsys.com
Cc: netdev@vger.kernel.org, Joao.Pinto@synopsys.com,
peppe.cavallaro@st.com, alexandre.torgue@st.com,
mcoquelin.stm32@gmail.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] net: stmmac: CPU Performance Improvements
Date: Thu, 14 Nov 2019 13:34:08 -0800 (PST) [thread overview]
Message-ID: <20191114.133408.708754856568136468.davem@davemloft.net> (raw)
In-Reply-To: <BN8PR12MB326648DB784332302BD0D7A3D3710@BN8PR12MB3266.namprd12.prod.outlook.com>
From: Jose Abreu <Jose.Abreu@synopsys.com>
Date: Thu, 14 Nov 2019 10:59:14 +0000
> From: Jose Abreu <Jose.Abreu@synopsys.com>
> Date: Nov/13/2019, 15:12:01 (UTC+00:00)
>
>> CPU Performance improvements for stmmac. Please check bellow for results
>> before and after the series.
>
> Please do not apply this. I found an issue with patch 1/7 and I have
> some more changes that reduce even more the CPU usage.
Ok.
prev parent reply other threads:[~2019-11-14 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 15:12 Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 1/7] net: stmmac: Do not set RX IC bit if RX Coalesce is zero Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 2/7] net: stmmac: Setup a default RX Coalesce value instead of the minimum Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 3/7] net: stmmac: gmac4+: Enable the TBU Interrupt Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 4/7] net: stmmac: gmac4+: Remove uneeded computation for RFA/RFD Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 5/7] net: stmmac: xgmac: " Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 6/7] net: stmmac: Tune-up default coalesce settings Jose Abreu
2019-11-13 15:12 ` [PATCH net-next 7/7] net: stmmac: TX Coalesce should be per-packet Jose Abreu
2019-11-14 10:59 ` [PATCH net-next 0/7] net: stmmac: CPU Performance Improvements Jose Abreu
2019-11-14 21:34 ` David Miller [this message]
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=20191114.133408.708754856568136468.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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
all inboxes | Powered by JetHome®