From: "humin (Q)" <humin29@huawei.com>
To: <dev@dpdk.org>, <ferruh.yigit@intel.com>, <linuxarm@huawei.com>,
<bruce.richardson@intel.com>, <jerin.jacob@caviumnetworks.com>,
"Zhouchang (Forest)" <forest.zhouchang@huawei.com>,
lihuisong <lihuisong@huawei.com>,
"Zhouchang (Forest)" <forest.zhouchang@huawei.com>,
"liudongdong (C)" <liudongdong3@huawei.com>,
lihuisong <lihuisong@huawei.com>
Subject: [dpdk-dev] [RFC]lib/ethdev: fix data type in tc_rxq and tc_txq
Date: Sat, 8 Aug 2020 09:09:23 +0800 [thread overview]
Message-ID: <fe86002a-87af-8795-d638-d9776545b86d@huawei.com> (raw)
Currently, base and nb_queue in the tc_rxq and tc_txq information
of queue and TC mapping on both TX and RX paths are uint8_t.
The structure is as follows:
struct rte_eth_dcb_tc_queue_mapping {
/** rx queues assigned to tc per Pool */
struct {
uint8_t base;
uint8_t nb_queue;
} tc_rxq[ETH_MAX_VMDQ_POOL][ETH_DCB_NUM_TCS];
/** rx queues assigned to tc per Pool */
struct {
uint8_t base;
uint8_t nb_queue;
} tc_txq[ETH_MAX_VMDQ_POOL][ETH_DCB_NUM_TCS];
};
However, these datas will be truncated when queue number under a TC
is greater than 256. So it is necessay for data type of base and
nb_queue to change from uint8_t to uint16_t.
next reply other threads:[~2020-08-08 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 1:09 humin (Q) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-07 12:33 humin (Q)
2020-08-18 1:43 ` humin (Q)
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=fe86002a-87af-8795-d638-d9776545b86d@huawei.com \
--to=humin29@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=forest.zhouchang@huawei.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=lihuisong@huawei.com \
--cc=linuxarm@huawei.com \
--cc=liudongdong3@huawei.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).