From: Eric Dumazet <eric.dumazet@gmail.com>
To: Keyur Amrutbhai Patel <keyurp@xilinx.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: netif_receive_skb is taking long time
Date: Thu, 25 Oct 2018 10:32:13 -0700 [thread overview]
Message-ID: <5bc2b508-11aa-ddd9-5519-0116cdb16d09@gmail.com> (raw)
In-Reply-To: <BN6PR02MB2641D817810960AAE59B9CDEB7F70@BN6PR02MB2641.namprd02.prod.outlook.com>
Please do not top post, and use normal quoting.
On 10/25/2018 10:22 AM, Keyur Amrutbhai Patel wrote:
> Hi Eric,
>
> First of all thank you for replying and giving some spotlight.
>
> First step would be to read Documentation/networking/scaling.txt and see if anything there helps.
> - This is good article. I had gone through it. Any suggestion on RSS? How to configure it? Do I need to take care anything specially in my NIC driver?
Just read the page and apply the various configurations.
>
> Have you tried to profile the kernel and see if some contention or hot function appears ?
> - I have added time stampings in different functions. That is how I came to know that almost ~3375 neno seconds are used by just " netif_receive_skb " don’t know why. With less than that time my DMA operation is finishes and descriptors are managed.
> Current time consuming function are " netif_receive_skb " and " napi_alloc_skb " these two function calls are taking maximum about of time
>
So... networking spend more time in upper stacks than a driver.
A driver does almost nothing, just passing around bits that that NIC put in memory.
In most workloads, a driver would not use more than 5% of total cpu cycles.
Now, if all you need is to impress your friends/boss about some
crazy number of RX packets per second,
just do not allocate skbs, and not call netif_receive_skb(),
use something like XDP to drop incoming frames :)
> Maybe use a faster cpu, or remove not needed features like too heavy netfilter rules.
> - I am using Intex Xeon Platinum series processors. These are fast enough CPUs available in market with 64 cores. 2 CPU nodes (each has 32 core)
>
> We can not really answer your question, you do not provide enough information.
> - Please let me know what additional details you need. We have 6 queues in HW. Each is mapped to MSI-X vector. Each vector is giving interrupt on different CPU. From interrupt I am scheduling napi and from napi poll function I am getting DMA page and constructing skb and passing it to network layer with "netif_receive_skb".
>
> Let me know additional details which are required.
>
> Regards,
> Keyur
>
> -----Original Message-----
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Sent: Thursday, October 25, 2018 10:38 PM
> To: Keyur Amrutbhai Patel <keyurp@xilinx.com>; netdev@vger.kernel.org
> Subject: Re: netif_receive_skb is taking long time
>
> EXTERNAL EMAIL
>
> On 10/25/2018 08:39 AM, Keyur Amrutbhai Patel wrote:
>> Hi,
>>
>> In my NIC driver "netif_receive_skb" is taking too long time. Almost 3375 neno seconds. Which is more than whole packet processing from interrupt.
>>
>> Could anyone please help me to understand what could be the reason behind this? How to solve it to take minimum time?
>>
>> Is there any standard calls which we need to follow in order to get faster performance?
>>
>
> First step would be to read Documentation/networking/scaling.txt and see if anything there helps.
>
> Have you tried to profile the kernel and see if some contention or hot function appears ?
>
> Maybe use a faster cpu, or remove not needed features like too heavy netfilter rules.
>
> We can not really answer your question, you do not provide enough information.
>
next prev parent reply other threads:[~2018-10-26 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 15:39 netif_receive_skb is taking long time Keyur Amrutbhai Patel
2018-10-25 17:05 ` Keyur Amrutbhai Patel
2018-10-25 17:08 ` Eric Dumazet
2018-10-25 17:22 ` Keyur Amrutbhai Patel
2018-10-25 17:32 ` Eric Dumazet [this message]
2018-10-25 17:43 ` David Miller
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=5bc2b508-11aa-ddd9-5519-0116cdb16d09@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=keyurp@xilinx.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