From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net v1] net/sched: Don't print dump stack in event of transmission timeout
Date: Mon, 13 Apr 2020 11:01:42 +0000 [thread overview]
Message-ID: <BN8PR12MB3266B788233057BB024B92B3D3DD0@BN8PR12MB3266.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200413105408.GJ334007@unreal>
From: Leon Romanovsky <leon@kernel.org>
Date: Apr/13/2020, 11:54:08 (UTC+00:00)
> Sorry, if I misunderstood you, but you are proposing to count traffic, right?
>
> If yes, RDMA traffic bypasses the SW stack and not visible to the kernel, hence
> the BQL will count only ETH portion of that mixed traffic, while RDMA traffic
> is the one who "blocked" transmission channel (QP in RDMA terminology).
Sorry but you don't mention in your commit message that this is RDMA
specific so that's why I brought up the topic of BQL. Apologies for the
misunderstood.
---
Thanks,
Jose Miguel Abreu
next prev parent reply other threads:[~2020-04-13 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 6:08 [PATCH net v1] net/sched: Don't print dump stack in event of transmission timeout Leon Romanovsky
2020-04-12 18:59 ` Jakub Kicinski
2020-04-12 19:23 ` Leon Romanovsky
2020-04-13 4:19 ` David Miller
2020-04-13 5:03 ` Leon Romanovsky
2020-04-13 9:01 ` Jose Abreu
2020-04-13 10:20 ` Leon Romanovsky
2020-04-13 10:37 ` Jose Abreu
2020-04-13 10:54 ` Leon Romanovsky
2020-04-13 11:01 ` Jose Abreu [this message]
2020-04-13 11:25 ` Leon Romanovsky
2020-04-13 17:22 ` Cong Wang
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=BN8PR12MB3266B788233057BB024B92B3D3DD0@BN8PR12MB3266.namprd12.prod.outlook.com \
--to=jose.abreu@synopsys.com \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).