DPDK usage discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How L2 broadcast is handled under rte_flow?
Date: Thu, 29 Aug 2019 12:11:40 +0900	[thread overview]
Message-ID: <20190829121139.17DE.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <20190814145603.D122.17218CA3@ntt-tx.co.jp_1>

Hello Experts,

Can somebody help me?
(Or many people still enjoy summer vacation?)

I think it is very interesting question
how NIC handles L2 broadcast when multiple queues are setup.

Or are there any way(DPDK API) to set NIC to assign all rx queues
when receiving L2 broadcast?

Thanks in advance.
BR,
Hideyuki Yamashita
NTT TechnoCross


> Hello Experts,
> 
> I have basic questions on how L2 broadcast is handled under rte_flow.
> 
> [Question1]
> 
> To which queue L2 broadcast packet will be received?
> 
> testpmd> flow create 0 ingress pattern eth dst is 11:22:33:44:55:66 type mask 0xffff / end actions queue index 1 / end
> testpmd> flow create 0 ingress pattern eth dst is 22:33:44:55:66:77 type mask 0xffff / end actions queue index 2 / end
> 
> My expectation is both queue 1 and queue 2 receive broadcast(dst MAC is
> FF:FF:FF:FF:FF:FF).
> Or only default queue (queue 0 ) receive the packet?
> 
> If we assume NIC act as switching hub and queues are ports,
> broadcast packets will be flooded to all available ports.
> Let us assume the situation that there exists software switch
> which act like switching hub (deliver packets based on dst MAC),
> and I want the function offload to NIC via rte_flow.
> 
> [Question2]
> What happens if VLAN is involved?
> 
> My expectation is as following:
> If receive broadcast packet (dst is FF:FF:FF:FF:FF:FF) for specific vlan,
> all queues related to this vlan id will receive the broadcast packet.
> Is my understanding correct?
> 
> It may depends on each rte_flow implementations.
> But if there is a rule in common among various NICs, I want to know.



      reply	other threads:[~2019-08-29  3:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  6:08 [dpdk-users] Why flow can not be created? Hideyuki Yamashita
2019-07-22 12:48 ` Ye Xiaolong
2019-07-23  6:26   ` Hideyuki Yamashita
2019-07-30 10:37     ` Hideyuki Yamashita
2019-07-30 12:25       ` Adrien Mazarguil
2019-07-31  2:30         ` Hideyuki Yamashita
2019-08-02  6:06           ` Hideyuki Yamashita
2019-08-06  9:12             ` Adrien Mazarguil
2019-08-06  9:59               ` Moti Haimovsky
2019-08-09  6:05               ` Hideyuki Yamashita
2019-08-14  5:56                 ` [dpdk-users] How L2 broadcast is handled under rte_flow? Hideyuki Yamashita
2019-08-29  3:11                   ` Hideyuki Yamashita [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=20190829121139.17DE.17218CA3@ntt-tx.co.jp_1 \
    --to=yamashita.hideyuki@ntt-tx.co.jp \
    --cc=users@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).