From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Gage Eads <gage.eads@intel.com>
Cc: dev@dpdk.org, nipun.gupta@nxp.com, hemant.agrawal@nxp.com,
harry.van.haaren@intel.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] eventdev: ease single-link queue config requirements
Date: Mon, 4 Sep 2017 11:39:14 +0530 [thread overview]
Message-ID: <20170904060913.GA17139@jerin> (raw)
In-Reply-To: <1502308684-28031-1-git-send-email-gage.eads@intel.com>
-----Original Message-----
> Date: Wed, 9 Aug 2017 14:58:04 -0500
> From: Gage Eads <gage.eads@intel.com>
> To: dev@dpdk.org
> CC: jerin.jacob@caviumnetworks.com, nipun.gupta@nxp.com,
> hemant.agrawal@nxp.com, harry.van.haaren@intel.com,
> bruce.richardson@intel.com
> Subject: [PATCH] eventdev: ease single-link queue config requirements
> X-Mailer: git-send-email 2.7.4
>
> Events sent through single-link queues are naturally in-order and
> atomic, without reordering or atomic scheduling. Logically the
> nb_atomic_flows and nb_atomic_order_sequences arguments don't apply to a
> single link queue, but applications must set these (depending on the queue
> config type) to bypass the is_valid_{ordered, atomic}_queue_conf() checks
> in the eventdev layer.
>
> This commit updates those is_valid_* functions to ignore queues with the
> SINGLE_LINK flag, to simplify their configuration.
>
> Signed-off-by: Gage Eads <gage.eads@intel.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2017-09-04 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 19:58 Gage Eads
2017-09-04 6:09 ` Jerin Jacob [this message]
2017-09-15 12:41 ` Jerin Jacob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170904060913.GA17139@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).