From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Harman Kalra <hkalra@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: check for interrupt context
Date: Mon, 18 Nov 2019 10:18:38 +0000 [thread overview]
Message-ID: <786783c2-e9aa-6f0a-8911-3a06133c3fc6@intel.com> (raw)
In-Reply-To: <1574019355-27695-1-git-send-email-hkalra@marvell.com>
On 17-Nov-19 7:36 PM, Harman Kalra wrote:
> Added an API to check if current execution is in interrupt
> context. This will be helpful to handle nested interrupt cases.
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
> ---
This is a great idea. It would be nice to add checks for is_intr()
inside rte_malloc routines, as currently attempting to rte_malloc (or
allocate anything) may lead to a deadlock. Is this intended for this
release, or future one?
--
Thanks,
Anatoly
prev parent reply other threads:[~2019-11-18 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 19:36 Harman Kalra
2019-11-17 20:03 ` Stephen Hemminger
2019-11-18 7:43 ` [dpdk-dev] [PATCH v2] eal: add API to check if its " Harman Kalra
2019-11-17 20:04 ` [dpdk-dev] [PATCH] eal: check for " Stephen Hemminger
2019-11-18 10:18 ` Burakov, Anatoly [this message]
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=786783c2-e9aa-6f0a-8911-3a06133c3fc6@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.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).