From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "Eads, Gage" <gage.eads@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
"jerin.jacon@caviumnetworks.com" <jerin.jacon@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] event/sw: allow fwd and rel when out of credits
Date: Mon, 16 Oct 2017 17:03:26 +0530 [thread overview]
Message-ID: <20171016113325.GA17937@jerin> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA640C78082@IRSMSX102.ger.corp.intel.com>
-----Original Message-----
> Date: Mon, 11 Sep 2017 08:52:44 +0000
> From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
> To: "Eads, Gage" <gage.eads@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
> CC: "jerin.jacon@caviumnetworks.com" <jerin.jacon@caviumnetworks.com>
> Subject: Re: [dpdk-dev] [PATCH] event/sw: allow fwd and rel when out of
> credits
>
> > From: Eads, Gage
> > Sent: Friday, September 8, 2017 7:08 PM
> > To: dev@dpdk.org
> > Cc: Van Haaren, Harry <harry.van.haaren@intel.com>;
> > jerin.jacon@caviumnetworks.com
> > Subject: [PATCH] event/sw: allow fwd and rel when out of credits
> >
> > When forwarding or releasing events, the operation would fail if the port
> > has 0 inflight credits and cannot acquire more, or the inflight count
> > exceeds the port's new event threshold.
> >
> > This patch fixes that by counting the number of new events in the burst,
> > and applying the credit and new event threshold checks accordingly.
> >
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
>
> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
Applied to dpdk-next-eventdev/master. Thanks.
next prev parent reply other threads:[~2017-10-16 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 18:07 Gage Eads
2017-09-11 8:52 ` Van Haaren, Harry
2017-10-16 11:33 ` Jerin Jacob [this message]
2017-09-11 8:55 ` Van Haaren, Harry
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=20171016113325.GA17937@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacon@caviumnetworks.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).