DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chen, Jing D" <jing.d.chen@intel.com>
To: "He, Shaopeng" <shaopeng.he@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] fm10k: enable PCIe port level Loopback Suppression
Date: Fri, 5 Feb 2016 09:25:02 +0000	[thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D0443D022@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1454589801-691-1-git-send-email-shaopeng.he@intel.com>

Hi, 

Best Regards,
Mark


> -----Original Message-----
> From: He, Shaopeng
> Sent: Thursday, February 04, 2016 8:43 PM
> To: dev@dpdk.org
> Cc: Chen, Jing D; Wang, Xiao W; He, Shaopeng
> Subject: [PATCH v2] fm10k: enable PCIe port level Loopback Suppression
> 
> In FM10K, a single PCIe port can derive out a few logical ports,
> like SRIOV PF/VF devices, VMDQ objects. To better manage them, FM10K
> silicon assigned a Unique GLORT ID to each logical ports.
> When a logical port sends a broadcast packet, the silicon will flood
> it to all Logical ports, including the one sent the broadcast packet.
> To prevent this, silicon has a rxq register to fill the glort id of
> the logical port that queue binds to.
> FM10K has a switch core inside, which has another loopback suppression
> mechanism in the switch level. Switch level loopback suppression mostly
> works for the ether port traffic.
> This patch assigns a SGLORT for each RX queue, and enables PCIe port
> level Loopback Suppression.
> 
> Signed-off-by: Shaopeng He <shaopeng.he@intel.com>
Acked-by : Jing Chen <jing.d.chen@intel.com>

  reply	other threads:[~2016-02-05  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 12:43 Shaopeng He
2016-02-05  9:25 ` Chen, Jing D [this message]
2016-02-25 21:45   ` Bruce Richardson

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=4341B239C0EFF9468EE453F9E9F4604D0443D022@shsmsx102.ccr.corp.intel.com \
    --to=jing.d.chen@intel.com \
    --cc=dev@dpdk.org \
    --cc=shaopeng.he@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).