From: Thomas Monjalon <thomas@monjalon.net>
To: "shahafs@mellanox.com" <shahafs@mellanox.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Boccassi, Luca" <luca.boccassi@intl.att.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"remy.horton@intel.com" <remy.horton@intel.com>,
"mohammad.abdul.awal@intel.com" <mohammad.abdul.awal@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [PATCH] doc: announce ABI change to support VF representors
Date: Wed, 14 Feb 2018 17:50:39 +0100 [thread overview]
Message-ID: <4986406.oWqD7VKg3u@xps> (raw)
In-Reply-To: <20180214155442.GA9407@jerin>
> > > This is following the RFC being discussed and targets 18.05
> > >
> > > http://dpdk.org/ml/archives/dev/2018-January/085716.html
> > >
> > > Cc: declan.doherty@intel.com
> > > Cc: mohammad.abdul.awal@intel.com
> > > Cc: ferruh.yigit@intel.com
> > > Cc: remy.horton@intel.com
> > >
> > > Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> > > ---
> > > +* ethdev: A work is being planned for 18.05 to expose VF port
> > > representors
> > > + as a mean to perform control and data path operation on the
> > > different VFs.
> > > + As VF representor is an ethdev port, new fields are needed in
> > > order to map
> > > + between the VF representor and the VF or the parent PF. Those new
> > > fields
> > > + are to be included in ``rte_eth_dev_info`` struct.
> >
> > Acked-by: Luca Boccassi <luca.boccassi@intl.att.com>
> > Acked-by: Alex Zelezniak <alexz@att.com>
>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied
prev parent reply other threads:[~2018-02-14 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 12:32 [PATCH] doc: announce ABI change to support VF representors Shahaf Shuler
2018-02-14 13:50 ` Thomas Monjalon
2018-02-14 13:54 ` Doherty, Declan
2018-02-14 14:50 ` Remy Horton
2018-02-14 15:27 ` Boccassi, Luca
2018-02-14 15:54 ` Jerin Jacob
2018-02-14 16:50 ` Thomas Monjalon [this message]
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=4986406.oWqD7VKg3u@xps \
--to=thomas@monjalon.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=luca.boccassi@intl.att.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=remy.horton@intel.com \
--cc=shahafs@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.