From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 4BBBD200 for ; Mon, 16 Jul 2018 14:59:24 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jul 2018 05:59:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,361,1526367600"; d="scan'208";a="56882018" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.107]) by orsmga007.jf.intel.com with SMTP; 16 Jul 2018 05:58:55 -0700 Received: by (sSMTP sendmail emulation); Mon, 16 Jul 2018 13:58:54 +0100 Date: Mon, 16 Jul 2018 13:58:53 +0100 From: Bruce Richardson To: Sungho Hong Cc: dev@dpdk.org Message-ID: <20180716125853.GA1488@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.10.0 (2018-05-17) Subject: Re: [dpdk-dev] Questions about locating the rte_mbuf payload X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2018 12:59:24 -0000 On Fri, Jul 13, 2018 at 10:41:31PM -0700, Sungho Hong wrote: > Hello I have sent the packet with the data "hellohellohello*" > in a message struct using DPDK > > struct message{ > data[PKT_SIZE] > } > > I am sending this data from a client to server, and the server receives > this data. the data received in the server can be viewed from the packet > dump provided by DPDK. You can see the data I am sending "hello"s right at > the bottom of the log > How exactly are you sending this data? What is the code for creating the packet to send? The code you sent looks ok for reading the packet, but the position in the mbuf also depends on what the packet being sent looks like, which is dependent on how the packet is created on the sender side. Regards, /Bruce