All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "WanRenyong" <wanry@yunsilicon.com>
Cc: <dev@dpdk.org>, <ferruh.yigit@amd.com>, <thomas@monjalon.net>,
	<andrew.rybchenko@oktetlabs.ru>, <qianr@yunsilicon.com>,
	<nana@yunsilicon.com>, <zhangxx@yunsilicon.com>,
	<xudw@yunsilicon.com>, <jacky@yunsilicon.com>,
	<weihg@yunsilicon.com>
Subject: Re: [PATCH v4 02/15] net/xsc: add xsc device initialization
Date: Fri, 3 Jan 2025 10:58:51 -0800	[thread overview]
Message-ID: <20250103105851.1dde1210@pi5> (raw)
In-Reply-To: <20250103150407.1529663-3-wanry@yunsilicon.com>

On Fri, 03 Jan 2025 23:04:08 +0800
"WanRenyong" <wanry@yunsilicon.com> wrote:

> +struct xsc_hwinfo {
> +	uint8_t valid; /* 1: current phy info is valid, 0 : invalid */
> +	uint32_t pcie_no; /* pcie number , 0 or 1 */
> +	uint32_t func_id; /* pf glb func id */
> +	uint32_t pcie_host; /* host pcie number */
> +	uint32_t mac_phy_port; /* mac port */
> +	uint32_t funcid_to_logic_port_off; /* port func id offset */
> +	uint16_t lag_id;
> +	uint16_t raw_qp_id_base;
> +	uint16_t raw_rss_qp_id_base;
> +	uint16_t pf0_vf_funcid_base;
> +	uint16_t pf0_vf_funcid_top;
> +	uint16_t pf1_vf_funcid_base;
> +	uint16_t pf1_vf_funcid_top;
> +	uint16_t pcie0_pf_funcid_base;
> +	uint16_t pcie0_pf_funcid_top;
> +	uint16_t pcie1_pf_funcid_base;
> +	uint16_t pcie1_pf_funcid_top;
> +	uint16_t lag_port_start;
> +	uint16_t raw_tpe_qp_num;
> +	int send_seg_num;
> +	int recv_seg_num;
> +	uint8_t on_chip_tbl_vld;
> +	uint8_t dma_rw_tbl_vld;
> +	uint8_t pct_compress_vld;
> +	uint32_t chip_version;
> +	uint32_t hca_core_clock;
> +	uint8_t mac_bit;
> +	uint8_t esw_mode;
> +};

Can you rearrange elements in this structure so there are less holes?
Or is it shared with the hardware. 

Unless you need negative value as a sentinel, avoid use of int where unsigned could be used for
seg_num.

  reply	other threads:[~2025-01-03 18:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 15:04 [PATCH v4 00/15] XSC PMD for Yunsilicon NICs WanRenyong
2025-01-03 15:04 ` [PATCH v4 01/15] net/xsc: add xsc PMD framework WanRenyong
2025-01-03 19:00   ` Stephen Hemminger
2025-01-06  1:36     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 02/15] net/xsc: add xsc device initialization WanRenyong
2025-01-03 18:58   ` Stephen Hemminger [this message]
2025-01-06  3:29     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 03/15] net/xsc: add xsc mailbox WanRenyong
2025-01-03 15:04 ` [PATCH v4 04/15] net/xsc: add xsc dev ops to support VFIO driver WanRenyong
2025-01-03 19:02   ` Stephen Hemminger
2025-01-06  1:53     ` WanRenyong
2025-01-03 19:04   ` Stephen Hemminger
2025-01-06  2:01     ` WanRenyong
2025-01-03 19:06   ` Stephen Hemminger
2025-01-06  2:02     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 05/15] net/xsc: add PCT interfaces WanRenyong
2025-01-03 15:04 ` [PATCH v4 06/15] net/xsc: initialize xsc representors WanRenyong
2025-01-03 15:04 ` [PATCH v4 07/15] net/xsc: add ethdev configure and RSS ops WanRenyong
2025-01-03 19:14   ` Stephen Hemminger
2025-01-06  2:20     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 08/15] net/xsc: add Rx and Tx queue setup WanRenyong
2025-01-03 15:04 ` [PATCH v4 09/15] net/xsc: add ethdev start WanRenyong
2025-01-03 19:17   ` Stephen Hemminger
2025-01-06  3:01     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 10/15] net/xsc: add ethdev stop and close WanRenyong
2025-01-03 15:04 ` [PATCH v4 11/15] net/xsc: add ethdev Rx burst WanRenyong
2025-01-03 15:04 ` [PATCH v4 12/15] net/xsc: add ethdev Tx burst WanRenyong
2025-01-03 15:04 ` [PATCH v4 13/15] net/xsc: add basic stats ops WanRenyong
2025-01-03 15:04 ` [PATCH v4 14/15] net/xsc: add ethdev infos get WanRenyong
2025-01-03 19:22   ` Stephen Hemminger
2025-01-06  4:03     ` WanRenyong
2025-01-03 15:04 ` [PATCH v4 15/15] net/xsc: add ethdev link and MTU ops WanRenyong

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=20250103105851.1dde1210@pi5 \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jacky@yunsilicon.com \
    --cc=nana@yunsilicon.com \
    --cc=qianr@yunsilicon.com \
    --cc=thomas@monjalon.net \
    --cc=wanry@yunsilicon.com \
    --cc=weihg@yunsilicon.com \
    --cc=xudw@yunsilicon.com \
    --cc=zhangxx@yunsilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.