From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 707811B34A for ; Mon, 23 Oct 2017 10:04:30 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2017 01:04:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,421,1503385200"; d="scan'208";a="165828831" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga005.fm.intel.com with ESMTP; 23 Oct 2017 01:04:28 -0700 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 23 Oct 2017 09:04:27 +0100 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.180]) by irsmsx155.ger.corp.intel.com ([169.254.14.169]) with mapi id 14.03.0319.002; Mon, 23 Oct 2017 09:04:27 +0100 From: "Van Haaren, Harry" To: Pavan Nikhilesh Bhagavatula CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH 1/3] evendev: fix inconsistency in event queue config Thread-Index: AQHTQ1xG14824kEOX0adMmqVvtGmd6Lse9HggAAJnYCAAHYPIIAAGu0AgAQNx6A= Date: Mon, 23 Oct 2017 08:04:26 +0000 Message-ID: References: <1507814147-8223-1-git-send-email-pbhagavatula@caviumnetworks.com> <20171020103032.GA7404@PBHAGAVATULA-LT> <20171020190927.GA18722@PBHAGAVATULA-LT> In-Reply-To: <20171020190927.GA18722@PBHAGAVATULA-LT> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTgwZDJkMjItNWY2Ni00N2E2LWJmNTktYjExZjM3MmJlYzFjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImtTOTFIRzE0MU40eXVlTFg3WkY1cFNtNmdjRTVwXC81NCtoT1htK2RValwvTT0ifQ== x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 1/3] evendev: fix inconsistency in event queue config 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, 23 Oct 2017 08:04:31 -0000 > From: Pavan Nikhilesh Bhagavatula [mailto:pbhagavatula@caviumnetworks.com= ] > Sent: Friday, October 20, 2017 8:09 PM > To: Van Haaren, Harry > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 1/3] evendev: fix inconsistency in event > queue config >=20 > On Fri, Oct 20, 2017 at 04:38:57PM +0000, Van Haaren, Harry wrote: > > Sure, I see two sane-ish options: > > > > 1) Return an error code from get_attr(), which actually means "ALL TYPE= S". > Feels a bit weird, because an error value is really a valid return. > > > > 2) Return UINT_MAX (aka, -1) as the scheduling value. Applications that > use/care about the scheduling type must check, others can ignore it. > > > > I'm not sure which of these is the better/less-bad solution. Opinions? = -H > > >=20 > I think 1st option would be good, we could use ENOTUNIQ to represent that > the > queue type is "ALL TYPE". >=20 > Thoughts? OK with me!