From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id C040A6C93 for ; Sat, 20 Aug 2016 09:00:11 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP; 20 Aug 2016 00:00:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,548,1464678000"; d="scan'208";a="6025" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 20 Aug 2016 00:00:10 -0700 Received: from fmsmsx101.amr.corp.intel.com (10.18.124.199) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 20 Aug 2016 00:00:10 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx101.amr.corp.intel.com (10.18.124.199) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 20 Aug 2016 00:00:10 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.147]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.181]) with mapi id 14.03.0248.002; Sat, 20 Aug 2016 15:00:08 +0800 From: "Lu, Wenzhuo" To: Adrien Mazarguil , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC v2] ethdev: introduce generic flow API Thread-Index: AQHR+lCLL4VWomGdJ0KZBDGB7j0h8qBRadmQ Date: Sat, 20 Aug 2016 07:00:07 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09090349C5B4@shsmsx102.ccr.corp.intel.com> References: <20160705181646.GO7621@6wind.com> <31d00ae664a3aba26a2c703f53bcc6a5b11502b7.1471632644.git.adrien.mazarguil@6wind.com> In-Reply-To: <31d00ae664a3aba26a2c703f53bcc6a5b11502b7.1471632644.git.adrien.mazarguil@6wind.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTU1OWU4YmMtMDExYi00NWU4LWJjNDItNGJhNjdkZDYzOTU2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlFtdUlVN01UT2NCUUgyU25uTG9wZEdHZHNLN2VPUUtwMjNQb1JTeGNCdVk9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC v2] ethdev: introduce generic flow API 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: Sat, 20 Aug 2016 07:00:12 -0000 Hi Adrien, Thanks for the V2.=20 May I ask a question that may a little out of the scope here. As currently = we don't store all the flow rules in the driver of Intel NICs, we're trying= to fill this gap. Considering we need to order the flow rules by the prior= ity, I think it's better to introduce avl tree or RB tree or something like= that. We can transplant the avl tree code from FreeBSD. But it doesn't mak= e sense to put it in the PMD. As you mentioned you'll provide some common c= ode in the lib, will you provide avl tree or something similar in the commo= n code? If you have already done it, we need not waste time to do the same = thing again :)