All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, "Gaëtan Rivet" <gaetan.rivet@6wind.com>,
	"Raslan Darawsheh" <rasland@mellanox.com>,
	jingjing.wu@intel.com, salehals@mellanox.com
Subject: Re: [PATCH] app/testpmd: app/testpmd: add device removal command
Date: Mon, 28 Aug 2017 13:00:24 +0200	[thread overview]
Message-ID: <48531686.15frCTT1P0@xps> (raw)
In-Reply-To: <2200a72f-92bb-c4e6-db9d-b00961fc328b@intel.com>

28/08/2017 12:30, Ferruh Yigit:
> On 8/28/2017 10:55 AM, Gaëtan Rivet wrote:
> > Hi Raslan,
> > 
> > Redoing the review with the remarks from Thomas in mind.
> > 
> > On Wed, Aug 23, 2017 at 05:37:04PM +0300, Raslan Darawsheh wrote:
> >> Added hotplug in testpmd, to be able to test hotplug function
> >> in the PMD's.
> >>
> >> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
> >> ---
> >>  app/test-pmd/cmdline.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> >>  app/test-pmd/testpmd.c | 18 ++++++++++++++++++
> >>  app/test-pmd/testpmd.h |  1 +
> >>  3 files changed, 63 insertions(+)
> >>
> >> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> >> index cd8c358..b32a368 100644
> >> --- a/app/test-pmd/cmdline.c
> >> +++ b/app/test-pmd/cmdline.c
> >> @@ -716,6 +716,9 @@ static void cmd_help_long_parsed(void *parsed_result,
> >>  			"port config (port_id|all) l2-tunnel E-tag"
> >>  			" (enable|disable)\n"
> >>  			"    Enable/disable the E-tag support.\n\n"
> >> +
> >> +			" device remove (device)\n"
> > 
> > I think (device) might be hard to understand for a user.
> > Maybe (device name)?
> 
> I am suspicious on adding new root level command to testpmd, it is
> getting bigger, each command looks OK on its own context, but as a whole
> app getting more confusing [1].

We can keep the root level "port" if we make clear that the impact
is beyond the port.

> Since dealing with device is kind of new, it can be OK to create new
> command tree, but there are already hotplug commands per port:
> "port attach #PCI|#VDEV_NAME"
> "port detach #P"
> 
> perhaps it can be good to keep "attach", "detach" keywords for device to
> be consistent?

Not sure.
Anyway ethdev attach and detach should be deprecated.
We are moving to a more correct design where hotplug is done at EAL level.

> "device attach #name"
> "device detach #name"
> 
> Also a show equivalent can be added to work in device level:
> "show device info"
> 
> 
> [1]
> http://dpdk.org/ml/archives/dev/2017-August/072764.html

  reply	other threads:[~2017-08-28 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 14:37 [PATCH] app/testpmd: app/testpmd: add device removal command Raslan Darawsheh
2017-08-23 15:09 ` Gaëtan Rivet
2017-08-23 16:18   ` Thomas Monjalon
2017-08-25  7:53     ` Gaëtan Rivet
2017-08-25  8:55       ` Thomas Monjalon
2017-08-28  9:55 ` Gaëtan Rivet
2017-08-28 10:30   ` Ferruh Yigit
2017-08-28 11:00     ` Thomas Monjalon [this message]
2017-08-28 11:12     ` Gaëtan Rivet
2017-09-07  8:17       ` Wu, Jingjing
2017-11-28 22:02         ` Ferruh Yigit
2017-12-03  9:32           ` Raslan Darawsheh

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=48531686.15frCTT1P0@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=jingjing.wu@intel.com \
    --cc=rasland@mellanox.com \
    --cc=salehals@mellanox.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.