DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arnon Warshavsky <arnon@qwilt.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: register rte_panic user callback
Date: Wed, 7 Mar 2018 13:02:30 +0200	[thread overview]
Message-ID: <CAKy9EB2ZfCf98V0O3pCPWe0eBwWFMvkv+HvQm-C1ToNTc6Sx5g@mail.gmail.com> (raw)
In-Reply-To: <4197355.YAsZy1EAlL@xps>

> > Can this really go into current release without deprecation notices?
>
> If such an exception is done, it must be approved by the technical board.
> We need to check few criterias:
>         - which functions need to be changed
>         - how the application is impacted
>         - what is the urgency
>
> If a panic is removed and the application is not already checking some
> error code, the execution will continue without considering the error.
>

> Some rte_panic could be probably removed without any impact on
> applications.
> Some rte_panic could wait for 18.08 with a notice in 18.05.
> If some rte_panic cannot wait, it must be discussed specifically.
>

Every panic removal must be handled all the way up in all call paths.
If not all instances can be removed at once in 18.05 (which seems to be the
case)
maybe we should keep the callback patch until all the remains are gone.

  reply	other threads:[~2018-03-07 11:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 18:28 Arnon Warshavsky
2018-03-07  8:32 ` Thomas Monjalon
2018-03-07  8:57   ` Arnon Warshavsky
2018-03-07  9:05   ` Burakov, Anatoly
2018-03-07  9:59     ` Thomas Monjalon
2018-03-07 11:02       ` Arnon Warshavsky [this message]
2018-03-07 15:04         ` Thomas Monjalon
2018-03-07 16:26           ` Arnon Warshavsky
2018-03-07 11:29       ` Burakov, Anatoly
2018-03-07 13:23         ` Arnon Warshavsky
2018-03-07 15:06           ` Thomas Monjalon
2018-03-07 16:31             ` Arnon Warshavsky
2018-03-07 17:17               ` 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=CAKy9EB2ZfCf98V0O3pCPWe0eBwWFMvkv+HvQm-C1ToNTc6Sx5g@mail.gmail.com \
    --to=arnon@qwilt.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).