From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ascas2.astri.local (unknown [14.136.245.194]) by dpdk.org (Postfix) with ESMTP id D302FB6AB for ; Wed, 27 May 2015 06:17:22 +0200 (CEST) X-Scanned-By-astrihk1: eMail scan performed by network-box X-Scanned-By-astrihk1: Network Box scan job 13122a53-32f5-493e-b5af-4b9c09589746 X-Scanned-By-astrihk1: Network Box message id d39cbb8e-a471-4645-af60-8843e32dfb20 Received: from ASDAG1.astri.local ([10.6.2.18]) by ascas2.astri.local ([fe80::b4b6:9137:e125:3db5%21]) with mapi id 14.03.0181.006; Wed, 27 May 2015 12:17:21 +0800 From: Lin XU To: "dev@dpdk.org" Thread-Topic: Re: [dpdk-dev] proposal: raw packet send and receive API for PMD driver Thread-Index: AdCYNAXWubQ1bFCmT6yzRxqBQO3F6A== Date: Wed, 27 May 2015 04:18:47 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.6.72] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] proposal: raw packet send and receive API for PMD driver 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: Wed, 27 May 2015 04:17:24 -0000 I think it is very important to decouple PMD driver with DPDK framework. (1) Currently, the rte_mbuf struct is too simple and hard to support com= plex application such as IPSEC, flow control etc. This key struct should be= extendable to support customer defined management header and hardware offl= oading feature. (2) To support more NICs. So, I thinks it time to add new API for PMD(a no radical way), and develope= r can add initial callback function in PMD for various upper layer protocol= procedures.