[dpdk-dev] [PATCH 1/3] evendev: fix inconsistency in event queue config
Van Haaren, Harry
harry.van.haaren at intel.com
Mon Oct 23 10:04:26 CEST 2017
> From: Pavan Nikhilesh Bhagavatula [mailto:pbhagavatula at caviumnetworks.com]
> Sent: Friday, October 20, 2017 8:09 PM
> To: Van Haaren, Harry <harry.van.haaren at intel.com>
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 1/3] evendev: fix inconsistency in event
> queue config
> 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 TYPES".
> 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
> I think 1st option would be good, we could use ENOTUNIQ to represent that
> queue type is "ALL TYPE".
OK with me!
More information about the dev