All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"ophirmu@mellanox.com" <ophirmu@mellanox.com>,
	"wisamm@mellanox.com" <wisamm@mellanox.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>
Subject: Re: [PATCH 5/5] app/testpmd: setup attached ports on probe event
Date: Wed, 24 Oct 2018 21:57:48 +0200	[thread overview]
Message-ID: <1592659.ocTt40gUXr@xps> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D17043@IRSMSX107.ger.corp.intel.com>

24/10/2018 18:13, Iremonger, Bernard:
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > +set port setup on
> > +~~~~~~~~~~~~~~~~~
> > +
> > +Select how to retrieve new ports created after "port attach" command.
> > +
> > +For each new port, a setup is done.
> > +It will find the probed ports via RTE_ETH_FOREACH_MATCHING_DEV loop in
> > +iterator mode, or via RTE_ETH_EVENT_NEW in event mode.
> > +
> 
> It would be useful to add an example command here (similar to other commands).

Do you mean something like this?

	testpmd> set port setup on (iterator|event)

  reply	other threads:[~2018-10-24 19:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 13:41 [PATCH 0/5] app/testpmd: improve attach/detach support Thomas Monjalon
2018-10-24 13:41 ` [PATCH 1/5] app/testpmd: check not detaching device twice Thomas Monjalon
2018-10-24 15:38   ` Iremonger, Bernard
2018-10-24 13:41 ` [PATCH 2/5] app/testpmd: merge ports list update functions Thomas Monjalon
2018-10-24 15:45   ` Iremonger, Bernard
2018-10-24 13:41 ` [PATCH 3/5] app/testpmd: check not configuring port twice Thomas Monjalon
2018-10-24 15:50   ` Iremonger, Bernard
2018-10-24 13:41 ` [PATCH 4/5] app/testpmd: move ethdev events registration Thomas Monjalon
2018-10-24 15:55   ` Iremonger, Bernard
2018-10-24 19:55     ` Thomas Monjalon
2018-10-25  8:54       ` Iremonger, Bernard
2018-10-25  8:58         ` Thomas Monjalon
2018-10-24 13:41 ` [PATCH 5/5] app/testpmd: setup attached ports on probe event Thomas Monjalon
2018-10-24 16:13   ` Iremonger, Bernard
2018-10-24 19:57     ` Thomas Monjalon [this message]
2018-10-25  8:58       ` Iremonger, Bernard
2018-10-25 15:11 ` [PATCH v2 0/5] app/testpmd: improve attach/detach support Thomas Monjalon
2018-10-25 15:11   ` [PATCH v2 1/5] app/testpmd: check not detaching device twice Thomas Monjalon
2018-10-25 15:11   ` [PATCH v2 2/5] app/testpmd: merge ports list update functions Thomas Monjalon
2018-10-25 15:11   ` [PATCH v2 3/5] app/testpmd: check not configuring port twice Thomas Monjalon
2018-10-25 15:11   ` [PATCH v2 4/5] app/testpmd: move ethdev events registration Thomas Monjalon
2018-10-25 16:05     ` Iremonger, Bernard
2018-10-25 15:11   ` [PATCH v2 5/5] app/testpmd: setup attached ports on probe event Thomas Monjalon
2018-10-25 16:07     ` Iremonger, Bernard
2018-10-26 12:46   ` [PATCH v2 0/5] app/testpmd: improve attach/detach support 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=1592659.ocTt40gUXr@xps \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=ophirmu@mellanox.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=wisamm@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.