From: <Parthiban.Veerasooran@microchip.com>
To: <kuba@kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<horms@kernel.org>, <saeedm@nvidia.com>,
<anthony.l.nguyen@intel.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <andrew@lunn.ch>,
<corbet@lwn.net>, <linux-doc@vger.kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<Horatiu.Vultur@microchip.com>, <ruanjinjie@huawei.com>,
<Steen.Hegelund@microchip.com>, <vladimir.oltean@nxp.com>,
<masahiroy@kernel.org>, <alexanderduyck@fb.com>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <rdunlap@infradead.org>,
<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<UNGLinuxDriver@microchip.com>,
<Thorsten.Kummermehr@microchip.com>, <Pier.Beruto@onsemi.com>,
<Selvamani.Rajagopal@onsemi.com>, <Nicolas.Ferre@microchip.com>,
<benjamin.bigler@bernformulastudent.ch>, <linux@bigler.io>,
<markku.vorne@kempower.com>
Subject: Re: [PATCH net-next v6 10/14] net: ethernet: oa_tc6: implement receive path to receive rx ethernet frames
Date: Tue, 20 Aug 2024 05:10:40 +0000 [thread overview]
Message-ID: <aa183159-81fc-4463-876b-00e749e18760@microchip.com> (raw)
In-Reply-To: <20240819154838.3efa04fa@kernel.org>
Hi Jakub,
On 20/08/24 4:18 am, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Mon, 19 Aug 2024 06:53:51 +0000 Parthiban.Veerasooran@microchip.com
> wrote:
>>> This is a bit unusual. If the core decides to drop the packet it will
>>> count the drop towards the appropriate statistic. The drivers generally
>>> only count their own drops, and call netif_rx() without checking the
>>> return value.
>>
>> The first version of this patch series didn't have this check. There was
>> a comment in the 1st version to check the return value and update the
>> statistics.
>>
>> https://lore.kernel.org/lkml/375fa9b4-0fb8-8d4b-8cb5-d8a9240d8f16@huawei.com/
>>
>> That was the reason why it was introduced in the v2 of the patch series
>> itself. It seems, somehow it got escaped from your RADAR from v2 to v5
>> :D.
>
> Sorry about that :( There's definitely a gap in terms of reviewing
> the work of reviewers :(
No problem, I understand that, I just wanted to let you know the reason.
Thanks a lot for reviewing the patches and the feedback to bring the
patches to a good shape. Please keep supporting.
>
>> Sorry, somehow I also missed to check it in the netdev core. Now I
>> understand that the rx drop handled in the core itself in the below link
>> using the function "dev_core_stats_rx_dropped_inc(skb->dev)".
>>
>> https://github.com/torvalds/linux/blob/master/net/core/dev.c#L4894
>>
>> Is my understanding correct? if so then I will remove this check in the
>> next version.
>
> Yes!
O.K. Thanks for the confirmation.
Best regards,
Parthiban V
next prev parent reply other threads:[~2024-08-20 5:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:25 [PATCH net-next v6 00/14] Add support for OPEN Alliance 10BASE-T1x MACPHY Serial Interface Parthiban Veerasooran
2024-08-12 10:25 ` [PATCH net-next v6 01/14] Documentation: networking: add OPEN Alliance 10BASE-T1x MAC-PHY serial interface Parthiban Veerasooran
2024-08-12 10:25 ` [PATCH net-next v6 02/14] net: ethernet: oa_tc6: implement register write operation Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 03/14] net: ethernet: oa_tc6: implement register read operation Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 04/14] net: ethernet: oa_tc6: implement software reset Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 05/14] net: ethernet: oa_tc6: implement error interrupts unmasking Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 06/14] net: ethernet: oa_tc6: implement internal PHY initialization Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 07/14] net: phy: microchip_t1s: add c45 direct access in LAN865x internal PHY Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 08/14] net: ethernet: oa_tc6: enable open alliance tc6 data communication Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 09/14] net: ethernet: oa_tc6: implement transmit path to transfer tx ethernet frames Parthiban Veerasooran
2024-08-16 16:55 ` Jakub Kicinski
2024-08-19 10:11 ` Parthiban.Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 10/14] net: ethernet: oa_tc6: implement receive path to receive rx " Parthiban Veerasooran
2024-08-16 17:01 ` Jakub Kicinski
2024-08-19 6:53 ` Parthiban.Veerasooran
2024-08-19 22:48 ` Jakub Kicinski
2024-08-20 5:10 ` Parthiban.Veerasooran [this message]
2024-08-12 10:26 ` [PATCH net-next v6 11/14] net: ethernet: oa_tc6: implement mac-phy interrupt Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 12/14] net: ethernet: oa_tc6: add helper function to enable zero align rx frame Parthiban Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 13/14] microchip: lan865x: add driver support for Microchip's LAN865X MAC-PHY Parthiban Veerasooran
2024-08-16 17:05 ` Jakub Kicinski
2024-08-19 7:12 ` Parthiban.Veerasooran
2024-08-12 10:26 ` [PATCH net-next v6 14/14] dt-bindings: net: add Microchip's LAN865X 10BASE-T1S MACPHY Parthiban Veerasooran
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=aa183159-81fc-4463-876b-00e749e18760@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Pier.Beruto@onsemi.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=Steen.Hegelund@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=benjamin.bigler@bernformulastudent.ch \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@bigler.io \
--cc=markku.vorne@kempower.com \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=saeedm@nvidia.com \
--cc=vladimir.oltean@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 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).