DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@nvidia.com>
To: Robin Jarry <rjarry@redhat.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Ilya Maximets <i.maximets@ovn.org>,
	David Marchand <david.marchand@redhat.com>,
	Aaron Conole <aconole@redhat.com>,
	Eelco Chaudron <echaudro@redhat.com>,
	Kevin Traynor <ktraynor@redhat.com>
Subject: RE: rte-flow: unmatched ingress traffic default action
Date: Tue, 18 Oct 2022 10:11:17 +0000	[thread overview]
Message-ID: <MW2PR12MB4666DC988179FDE90AEB71EFD6289@MW2PR12MB4666.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CNOY4D4CIRO3.2QHMZMI5EDKGC@marty>



> -----Original Message-----
> From: Robin Jarry <rjarry@redhat.com>
> Sent: Tuesday, 18 October 2022 12:36
> 
> Ori Kam, Oct 18, 2022 at 11:16:
> > > This is also in regular (non-isolated) mode?
> >
> > No, in non-isolated mode PMD will insert default rules based on the
> > configuration, for example matching on the mac/vlan
> 
> And eventually redirecting packets in queues following the RSS
> configuration?

Yes.

> 
> Do you think this is something that can be relied upon across different
> PMDs/NICs?

Unless I'm missing something, yes this is the basis of DPDK.
(I assume you are talking about non-isolated mode)


  reply	other threads:[~2022-10-18 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 14:48 Robin Jarry
2022-10-18  7:41 ` Ori Kam
2022-10-18  8:12   ` Robin Jarry
2022-10-18  9:16     ` Ori Kam
2022-10-18  9:36       ` Robin Jarry
2022-10-18 10:11         ` Ori Kam [this message]
2022-10-18 11:51           ` Robin Jarry

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=MW2PR12MB4666DC988179FDE90AEB71EFD6289@MW2PR12MB4666.namprd12.prod.outlook.com \
    --to=orika@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=echaudro@redhat.com \
    --cc=i.maximets@ovn.org \
    --cc=ktraynor@redhat.com \
    --cc=rjarry@redhat.com \
    --cc=thomas@monjalon.net \
    /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).