From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 676C69A for ; Mon, 6 Jan 2014 16:25:57 +0100 (CET) Received: by mail-wg0-f43.google.com with SMTP id k14so15966437wgh.10 for ; Mon, 06 Jan 2014 07:27:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=N/qWA0siVaTjmPxLjtnYEpO04Fxc4MMf6Q5DaScJVZw=; b=a5nknA8YVX7BjgictoOA7TjX4MYK3KIqOc6c+9Aua3fJ6TT4IrYdRxLBO2pZYXyaRg +i6HF5b7JpWg3omYEOlkvHgjV4PZbY5lHIxBykqvDIkz8IMSJGlQVVb6tCDYlHcCV+6Y 7XXAOOual3JB+q4+hrKp8g4lHOPA8LMEkI4p8lgbNToXtt8xMWI5q+E8vA8Z+w9JuwSq p5DRyZqPpLYJqZ1IeNOGB9rqxhI6KCG26E6djChUgSZvdI9atrJOxqR3iN19oZGmiolg DDD64jI93npO31u4SI52eKUpoEvOBuu6MBVKPXTeD29dFtuUBxgxiSgsDSOPp13YfG/w 0IyA== X-Gm-Message-State: ALoCoQkQanjnHe9HNUHW8CR49dU0d3LhHkF5VQPIXkdyvUmrwKU+rqI7hLVclP3VeThiTAut9yWz X-Received: by 10.180.108.42 with SMTP id hh10mr12917718wib.15.1389022028903; Mon, 06 Jan 2014 07:27:08 -0800 (PST) Received: from [10.16.0.189] (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id uq2sm42878951wjc.5.2014.01.06.07.27.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jan 2014 07:27:06 -0800 (PST) Message-ID: <52CACB48.7020100@6wind.com> Date: Mon, 06 Jan 2014 16:27:04 +0100 From: Ivan Boule User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: "Wang, Shawn" References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] question about PKT_RX_IPV4_HDR_EXT X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 15:25:57 -0000 On 12/26/2013 10:46 PM, Wang, Shawn wrote: > Hi: > > Can anyone explain more details about the rte_mbuf ol_flag : PKT_RX_IPV4_HDR_EXT? > The document said “RX packet with extended IPv4 header.” > But what is the extended IPv4 header looks like? What is the difference with normal IPv4 header? > Can anyone give me an example? > > Thanks a lot. > Wang, Shawn Hi, A extended IPv4 header is a IPv4 header with additional options, whose total header size is greater than 20 bytes. Intel 1GbE and 10Gbe Ethernet controllers are able to recognize such packets, and, in this case,set a dedicated flag into the RX descriptor where they store the packet. Then, to supply this hardware-detected packet characteristics to the upper-level application, the RX functions of DPDK PollMode Drivers of the 1GbE and 10Gbe Ethernet controllers set the PKT_RX_IPV4_HDR_EXT generic flag into the mbuf that contains the packet. Best regards, Ivan -- Ivan Boule 6WIND Development Engineer