From: Andrew Bainbridge <andbain@microsoft.com>
To: Konstantinos Schoinas <ece8537@upnet.gr>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Drop_Packet
Date: Mon, 6 Aug 2018 11:08:33 +0000 [thread overview]
Message-ID: <AM5PR83MB0196A3971EDFAE80791BA79EAE200@AM5PR83MB0196.EURPRD83.prod.outlook.com> (raw)
In-Reply-To: <32b56d20ae74d367acf6f42e4b9032e4@upnet.gr>
That's quite a broad question. A simple way is to not process packets you receive with rte_eth_rx_burst()! If you want the hardware to drop without the CPU seeing the packet, maybe you can setup a flow rule with a drop action. See https://doc.dpdk.org/guides/prog_guide/rte_flow.html.
________________________________
From: users <users-bounces@dpdk.org> on behalf of Konstantinos Schoinas <ece8537@upnet.gr>
Sent: 04 August 2018 12:06
To: users@dpdk.org
Subject: [dpdk-users] Drop_Packet
Hello,
How can i drop packets using dpdk? Is there any function that can help ?
Thanks for your time
prev parent reply other threads:[~2018-08-06 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 11:06 Konstantinos Schoinas
2018-08-06 11:08 ` Andrew Bainbridge [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=AM5PR83MB0196A3971EDFAE80791BA79EAE200@AM5PR83MB0196.EURPRD83.prod.outlook.com \
--to=andbain@microsoft.com \
--cc=ece8537@upnet.gr \
--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).