From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: No egressing packet Date: Wed, 16 Sep 2015 09:32:03 +0200 Message-ID: <1944265.eVANXui8GP@xps13> References: <55F88932.7020800@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Wu, Yiwen" Return-path: Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by dpdk.org (Postfix) with ESMTP id D86FC11F5 for ; Wed, 16 Sep 2015 09:33:11 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so59540401wic.1 for ; Wed, 16 Sep 2015 00:33:11 -0700 (PDT) In-Reply-To: <55F88932.7020800@gmail.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-09-15 17:10, Wu, Yiwen: > Hi all, > > I am new to dpdk. I am running a single forwarding program based on dpdk > 2.1.0. The program runs on a VM, binding on two interfaces. All it's > doing is to forward packets from one interface to another. All > ingressing packets are fine but there seems no egressing packets. I used > rte_eth_add_tx_callback to register a tx callback. The callback is able > to print the right egress packet but the destination is just not > receiving it (via tcpdump). Does anybody have the similar experience? > Any solution or hints will be great. You need to call rte_eth_tx_burst() instead of rte_eth_add_tx_callback(). For more information, please check the guide: http://dpdk.org/doc/guides/prog_guide/poll_mode_drv.html#poll-mode-driver You can also check this basic example: http://dpdk.org/browse/dpdk/tree/examples/skeleton/basicfwd.c