From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: stable@dpdk.org, dev@dpdk.org, stephen@networkplumber.org,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-stable] [PATCH] eal/mp: remove rte_panic and profanity
Date: Tue, 30 Oct 2018 10:31:58 +0000 [thread overview]
Message-ID: <e71ab321-d4c4-fe13-15fe-36b887909c8e@intel.com> (raw)
In-Reply-To: <4092104.WkhJc3HfzQ@xps>
On 26-Oct-18 9:41 PM, Thomas Monjalon wrote:
> 26/10/2018 16:55, Anatoly Burakov:
>> --- a/lib/librte_eal/common/eal_common_proc.c
>> +++ b/lib/librte_eal/common/eal_common_proc.c
>> + /*
>> + * set the alarm before sending message. there are two possible error
>> + * scenarios to consider here:
>> + *
>> + * - if the alarm set fails, we free the memory right there
>> + * - if the alarm set succeeds but sending message fails, then the alarm
>> + * will trigger and clean up the memory
>> + *
>> + * Even if the alarm triggers too early (i.e. immediately), we're still
>> + * holding the lock to pending requests queue, so the interrupt thread
>> + * will just spin until we release the lock, and either release the
>> + * memory, or doesn't find any pending requests in the queue because we
>> + * never added any due to send message failure.
>> + */
>> + if (rte_eal_alarm_set(ts->tv_sec * 1000000 + ts->tv_nsec / 1000,
>> + async_reply_handle, pending_req) < 0) {
>> + RTE_LOG(ERR, EAL, "Fail to set alarm for request %s:%s\n",
>> + dst, req->name);
>> + goto fail;
>> + }
>
> ret variable is not set and not initialized.
>
Oh, right. Apologies. Will send a v2.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-10-30 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180725182019.31518-4-stephen@networkplumber.org>
2018-10-26 14:55 ` Anatoly Burakov
2018-10-26 20:41 ` Thomas Monjalon
2018-10-30 10:31 ` Burakov, Anatoly [this message]
2018-11-13 18:03 ` [dpdk-stable] [PATCH v2] " Anatoly Burakov
2018-11-13 23:03 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=e71ab321-d4c4-fe13-15fe-36b887909c8e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.net \
/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).