DPDK patches and discussions
 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 14/15] net/xsc: add ethdev infos get
Date: Fri, 3 Jan 2025 11:22:03 -0800	[thread overview]
Message-ID: <20250103112203.48955f38@pi5> (raw)
In-Reply-To: <20250103150434.1529663-15-wanry@yunsilicon.com>

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

> +
> +static int
> +xsc_ethdev_infos_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *info)
> +{
> +	struct xsc_ethdev_priv *priv = TO_XSC_ETHDEV_PRIV(dev);
> +
> +	info->min_rx_bufsize = 64;
> +	info->max_rx_pktlen = 65536;
> +	info->max_lro_pkt_size = 0;
> +	info->max_rx_queues = 256;
> +	info->max_tx_queues = 1024;
> +	info->rx_desc_lim.nb_max = 4096;
> +	info->rx_desc_lim.nb_min = 16;
> +	info->tx_desc_lim.nb_max = 8192;
> +	info->tx_desc_lim.nb_min = 128;
> +
> +	info->rx_queue_offload_capa = xsc_get_rx_queue_offloads(dev);
> +	info->rx_offload_capa = info->rx_queue_offload_capa;
> +	info->tx_offload_capa = xsc_get_tx_port_offloads(dev);
> +
> +	info->if_index = priv->ifindex;
> +	info->speed_capa = priv->xdev->link_speed_capa;
> +	info->hash_key_size = XSC_RSS_HASH_KEY_LEN;
> +	info->tx_desc_lim.nb_seg_max = 8;
> +	info->tx_desc_lim.nb_mtu_seg_max = 8;
> +	info->switch_info.name = dev->data->name;
> +	info->switch_info.port_id = priv->representor_id;
> +	return 0;
> +}
> +

Note: that driver probably won't be at all functional without info_get
but as long as each patch builds, it doesn't matter to me what order the
patchset is in. Too hard to get a working driver at each step.

  reply	other threads:[~2025-01-03 19:22 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
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 [this message]
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=20250103112203.48955f38@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 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).