From: David Miller <davem@davemloft.net>
To: keyurp@xilinx.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: netif_receive_skb is taking long time
Date: Thu, 25 Oct 2018 10:43:10 -0700 (PDT) [thread overview]
Message-ID: <20181025.104310.1362475664274438273.davem@davemloft.net> (raw)
In-Reply-To: <BN6PR02MB2641D817810960AAE59B9CDEB7F70@BN6PR02MB2641.namprd02.prod.outlook.com>
From: Keyur Amrutbhai Patel <keyurp@xilinx.com>
Date: Thu, 25 Oct 2018 17:22:02 +0000
> Current time consuming function are " netif_receive_skb " and "
> napi_alloc_skb " these two function calls are taking maximum about
> of time
netif_receive_skb() calls the entire networking stack receive path.
So measuring it by itself it not very useful.
Use 'perf' or a similar tool to fully profile the kernel and get a
more detailed analysis.
prev parent reply other threads:[~2018-10-26 2:16 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
2018-10-25 17:43 ` 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=20181025.104310.1362475664274438273.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=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