From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Cc: "spp@dpdk.org" <spp@dpdk.org>
Subject: Re: [spp] [PATCH 1/3] spp_nfv: enable to patch ports with resource ID
Date: Thu, 22 Feb 2018 10:52:26 +0000 [thread overview]
Message-ID: <ef5615e8-dbb3-2753-b3dc-4dd1e13eecaa@intel.com> (raw)
In-Reply-To: <1518103072-4559-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
On 2/8/2018 3:17 PM, ogawa.yasufumi at lab.ntt.co.jp
(ogawa.yasufumi@lab.ntt.co.jp) wrote:
> From: "ogawa.yasufumi@lab.ntt.co.jp" <ogawa.yasufumi@lab.ntt.co.jp>
>
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> In spp, port ID is assigned as a number incrementally and the number of
> ID can be different from each sec processes. It depends on the order of
> adding ports.
>
> It is confusing to users for patching because each of sec processes has
> different port IDs but they refer the same resource. It might cause a
> mistake.
>
> This update enables users to patch ports with a combination of port type
> and number to identify resources as following.
> spp> sec 1;patch phy:0 ring:0
>
> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-02-22 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:17 ogawa.yasufumi
2018-02-08 15:17 ` [spp] [PATCH 2/3] spp: add validation for patch command ogawa.yasufumi
2018-02-08 15:17 ` [spp] [PATCH 3/3] spp_vm: enable to patch ports with resource ID ogawa.yasufumi
2018-02-22 10:52 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-29 12:44 [spp] [PATCH 1/3] spp_nfv: " ogawa.yasufumi
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=ef5615e8-dbb3-2753-b3dc-4dd1e13eecaa@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.org \
/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).