All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	"ferruh.yigit@linux.intel.com" <ferruh.yigit@linux.intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	"Jingjing Wu" <jingjing.wu@intel.com>,
	Bernard Iremonger <bernard.iremonger@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v3] app/testpmd: add device related cmds
Date: Mon, 22 Jul 2019 06:15:47 +0000	[thread overview]
Message-ID: <42546e3f-f398-89d1-6638-f9a5dada8552@marvell.com> (raw)
In-Reply-To: <VI1PR0401MB254120B40CAB0A26D578D87C89C40@VI1PR0401MB2541.eurprd04.prod.outlook.com>


On 7/22/2019 11:31 AM, Hemant Agrawal wrote:
> HI,
>> On 7/18/2019 6:27 AM, Nithin Kumar Dabilpuram wrote:
>>> Hi Ferruh,
>>>
>>> On 7/17/2019 10:21 PM, Ferruh Yigit wrote:
>>>> External Email
>>>>
>>>> ---------------------------------------------------------------------
>>>> - On 7/17/2019 1:30 PM, Nithin Dabilpuram wrote:
>>>>> With the latest published interface of
>>>>> rte_eal_hotplug_[add,remove](), and rte_eth_dev_close(),
>>>>> rte_eth_dev_close() would cleanup all the data structures of port's
>>>>> eth dev leaving the device common resource intact if
>>>>> RTE_ETH_DEV_CLOSE_REMOVE is set in dev flags.
>>>>>
>>>>> So a new command "detach device" (~hotplug remove) to work, with
>>>>> device identifier like "port attach" is added to be able to detach
>>>>> closed devices.
>>>>>
>>>>> Also to display currently probed devices, another command "show
>>>>> device info <identifier>|all" is also added as a part of this
>>>>> change.
>>>> In "show device info all" output [1] there are 'dpaa' & 'fslmc' logs
>>>> [2], do you know why we are getting them, can we get rid of them?
>>>>
>>> Is this issue sill there ?  I'm not able to see it in my setup.
>> Yes, still there. I can see them with latest next-net.
>>
> [Hemant] Patch is on the way.
Thanks.

  reply	other threads:[~2019-07-22  6:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 11:21 [dpdk-dev] [PATCH] app/testpmd: change port detach interface Nithin Dabilpuram
2019-05-14 15:39 ` Thomas Monjalon
2019-05-15  6:52   ` Nithin Dabilpuram
2019-05-15  7:27     ` Thomas Monjalon
2019-05-17  8:55       ` Nithin Dabilpuram
2019-05-17  8:59         ` Thomas Monjalon
2019-05-20 12:50           ` Nithin Dabilpuram
2019-05-29  8:16             ` Nithin Dabilpuram
2019-06-25  4:24               ` Nithin Dabilpuram
2019-07-02 15:58               ` Yigit, Ferruh
2019-07-03  5:05                 ` Nithin Dabilpuram
2019-07-10 13:07 ` [dpdk-dev] [PATCH v2] app/testpmd: add device related cmds Nithin Dabilpuram
2019-07-16 18:30   ` Ferruh Yigit
2019-07-17  8:08     ` [dpdk-dev] [EXT] " Nithin Kumar Dabilpuram
2019-07-17 12:30 ` [dpdk-dev] [PATCH v3] " Nithin Dabilpuram
2019-07-17 16:51   ` Ferruh Yigit
2019-07-18  5:27     ` [dpdk-dev] [EXT] " Nithin Kumar Dabilpuram
2019-07-19 19:00       ` Ferruh Yigit
2019-07-22  6:01         ` Hemant Agrawal
2019-07-22  6:15           ` Nithin Kumar Dabilpuram [this message]
2019-07-22 16:04             ` Ferruh Yigit
2019-07-17 16:54   ` [dpdk-dev] " Ferruh Yigit

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=42546e3f-f398-89d1-6638-f9a5dada8552@marvell.com \
    --to=ndabilpuram@marvell.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ferruh.yigit@linux.intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@intel.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.