patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <>
To: Bruce Richardson <>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/3] rawdev: allow calling info function for unknown rawdevs
Date: Tue, 07 Jul 2020 14:18:31 +0200
Message-ID: <227734353.nfkpUBtnmh@thomas> (raw)
In-Reply-To: <>

06/07/2020 12:31, Bruce Richardson:
> To call the rte_rawdev_info_get() function, the user currently has to know
> the underlying type of the device in order to pass an appropriate structure
> or buffer as the dev_private pointer in the info structure. By allowing a
> NULL value for this field, we can skip getting the device-specific info and
> just return the generic info - including the device name and driver, which
> can be used to determine the device type - to the user.
> This ensures that basic info can be get for all rawdevs, without knowing
> the type, and even if the info driver API call has not been implemented for
> the device.
> Cc:

This is a new feature. Why should it be backported?

  parent reply	other threads:[~2020-07-07 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2020-07-06 10:31 ` [dpdk-stable] " Bruce Richardson
2020-07-07  3:40   ` Hemant Agrawal
2020-07-07 12:18   ` Thomas Monjalon [this message]
2020-07-07 12:31     ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2020-07-06 10:31 ` [dpdk-stable] [PATCH 2/3] rawdev: return NUMA socket id to the user Bruce Richardson
2020-07-07  3:40   ` Hemant Agrawal
2020-07-07 12:23   ` Thomas Monjalon
2020-07-07 12:33     ` Bruce Richardson
2020-07-06 10:31 ` [dpdk-stable] [PATCH 3/3] rawdev: fix missing dump function in map file Bruce Richardson
2020-07-07  3:40   ` Hemant Agrawal

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=227734353.nfkpUBtnmh@thomas \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone