DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Vipin Varghese <vipin.varghese@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com,
	stephen1.byrne@intel.com, john.mcnamara@intel.com,
	declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc/tm: update support for pf only
Date: Mon, 15 Oct 2018 21:04:39 +0530	[thread overview]
Message-ID: <20181015153438.GA9264@jerin> (raw)
In-Reply-To: <20181015070451.35332-1-vipin.varghese@intel.com>

-----Original Message-----
> Date: Mon, 15 Oct 2018 12:34:51 +0530
> From: Vipin Varghese <vipin.varghese@intel.com>
> To: dev@dpdk.org, cristian.dumitrescu@intel.com
> CC: stephen1.byrne@intel.com, john.mcnamara@intel.com,
>  declan.doherty@intel.com, Vipin Varghese <vipin.varghese@intel.com>
> Subject: [dpdk-dev] [PATCH] doc/tm: update support for pf only
> X-Mailer: git-send-email 2.17.1
> 
> 
> Documentation is updated to highlight the support for DPDK ethernet
> interface for Traffic Manager is currently limited to PF only.

Why limit the specification to only PF devices? If a specific HW can
support only PF devices, it can register tm ops only to PF devices.
There are Hardwars which can support TM on VF as well, off course HW
capabilities may be different, It can expressed with exiting TM capabilities
structures.

  reply	other threads:[~2018-10-15 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  7:04 Vipin Varghese
2018-10-15 15:34 ` Jerin Jacob [this message]
2018-10-15 15:52   ` Dumitrescu, Cristian
2018-10-15 15:52 ` Dumitrescu, Cristian
2018-10-15  7:46 Vipin Varghese

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=20181015153438.GA9264@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=stephen1.byrne@intel.com \
    --cc=vipin.varghese@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 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).