From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8DB1E43381; Mon, 20 Nov 2023 18:48:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7D20742DD2; Mon, 20 Nov 2023 18:48:43 +0100 (CET) Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) by mails.dpdk.org (Postfix) with ESMTP id C56334027A for ; Mon, 20 Nov 2023 18:48:41 +0100 (CET) Received: by mail-qv1-f47.google.com with SMTP id 6a1803df08f44-677fe97ddf8so14160446d6.3 for ; Mon, 20 Nov 2023 09:48:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700502521; x=1701107321; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=mshnALntTH5XO4+yT5nwls3YeYbIJH14vMxd8H5xv+U=; b=W+SP0134inC2qjqDxNH1ZkTk1rKAF9UrTwVLb1rrY7Dp6KXt88hM3ZMv36hC1Y+sv+ EHrn1aQO302DQiw6jp4uCKB23hSH9yx+mzJl5MWEWpax0gZuajYcJBkEdZwInq4C4o8k QtzCX7oa62Chl+yOa/TnDWCvSI6l0yvcOtw6vE53ABf+e5PE1ozWAB5QZqtTJhLxF+5U 4NfoJ2vreYJnF8NfYuTwNNN/OEW9xaa1iKr7VAFnjXpl3Zmp15qlL/tGr8zZmlt1geYF 5CiLcrrbK3ERFO2xoglraWhX+94gtPLRgCtqAjYS9uAhOSUYNgW2EAQUyBYS5TFacSue tJbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700502521; x=1701107321; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mshnALntTH5XO4+yT5nwls3YeYbIJH14vMxd8H5xv+U=; b=de7yoWsHCpw//cOzEdLJlqUzTdXwgGRTcWM9Bg//eg0vYLFbHmRtyDxZZOZwfjE80h bPqMy9hVGd9Ek3xAmTTg9vYeBVDf6qGMdkcaXeip9RfDd0gnNFECmFEcpdfglkVx4ZgW gHz045g5cBEUQxzXkjw+EEr81lZm5LTkVhAH9UjgvynYO2M9IwFMFvDHvZTu0SmWs/Ie vbKPFCiE2oTNR3ydJwUrRaado3MbTcDcBhBVs8/+IpCMv3/eA/IlBO6u4aWlEio7DXIH 6OnOwt4lzbbXbuoIu1QQrf0QppihC1VN8OlED/NdhZu7hz/GUidX6poI7TfDMBeh5G4I q1uw== X-Gm-Message-State: AOJu0Yz9nhZLNo0pBQiH1jpWgjskhV00vxxNXhcN8/BBPec3LoZGdZRh zDWdozzldh0YhL2k2F9C5+2+CORoYmeGE7wifHQ= X-Google-Smtp-Source: AGHT+IFWuCB60LZsMDgJswS/h1jJYQ0SoRui4ZvhvYBamBqr5yE9sNzuGSRe3lYaMXKsgOBH5pVY17JHoLInp+6axF0= X-Received: by 2002:a0c:c98b:0:b0:679:d31a:83dd with SMTP id b11-20020a0cc98b000000b00679d31a83ddmr5282759qvk.41.1700502521091; Mon, 20 Nov 2023 09:48:41 -0800 (PST) MIME-Version: 1.0 References: <20231120172606.505579-1-bruce.richardson@intel.com> <20231120172606.505579-2-bruce.richardson@intel.com> In-Reply-To: <20231120172606.505579-2-bruce.richardson@intel.com> From: Jerin Jacob Date: Mon, 20 Nov 2023 23:18:14 +0530 Message-ID: Subject: Re: [PATCH 24.03 1/8] eventdev: add capability flags for supported sched types To: Bruce Richardson Cc: dev@dpdk.org, Jerin Jacob Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Mon, Nov 20, 2023 at 11:08=E2=80=AFPM Bruce Richardson wrote: > > Not all eventdev's support all scheduling types, for example, some may > only support atomic scheduling or others only support ordered > scheduling. There is currently no clear indication for each driver what > sched types it supports, so add capability flags to be indicated on > return from rte_event_dev_info_get() API. > > Similarly add the possible scheduling types to the capabilities table in > the docs. > > Signed-off-by: Bruce Richardson > --- > doc/guides/eventdevs/features/default.ini | 3 +++ > lib/eventdev/rte_eventdev.h | 21 +++++++++++++++++++++ > 2 files changed, 24 insertions(+) > > diff --git a/doc/guides/eventdevs/features/default.ini b/doc/guides/event= devs/features/default.ini > index e980ae134a..1cc4303fe5 100644 > --- a/doc/guides/eventdevs/features/default.ini > +++ b/doc/guides/eventdevs/features/default.ini > @@ -6,6 +6,9 @@ > ; the features table in the documentation. > ; > [Scheduling Features] > +atomic_scheduling =3D > +ordered_scheduling =3D > +parallel_scheduling =3D > queue_qos =3D > event_qos =3D > distributed_sched =3D > diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h > index ec9b02455d..9109de157e 100644 > --- a/lib/eventdev/rte_eventdev.h > +++ b/lib/eventdev/rte_eventdev.h > @@ -326,6 +326,27 @@ struct rte_event; > * than one. > */ > > +#define RTE_EVENT_DEV_CAP_ATOMIC (1ULL << 13) > +/**< Event device is capable of atomic scheduling. > + * When this flag is set, the application can configure queues with sche= duling type > + * atomic on this event device. > + * @see RTE_SCHED_TYPE_ATOMIC > + */ > + > +#define RTE_EVENT_DEV_CAP_ORDERED (1ULL << 13) > +/**< Event device is capable of ordered scheduling. > + * When this flag is set, the application can configure queues with sche= duling type > + * ordered on this event device. > + * @see RTE_SCHED_TYPE_ORDERED > + */ > + > +#define RTE_EVENT_DEV_CAP_PARALLEL (1ULL << 13) > +/**< Event device is capable of parallel scheduling. > + * When this flag is set, the application can configure queues with sche= duling type > + * parallel on this event device. > + * @see RTE_SCHED_TYPE_PARALLEL > + */ All the caps definition is 1ULL << 13. It should be unique per capa. > /* Event device priority levels */ > #define RTE_EVENT_DEV_PRIORITY_HIGHEST 0 > /**< Highest priority expressed across eventdev subsystem > -- > 2.39.2 >