All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: bernard.iremonger@intel.com, ferruh.yigit@intel.com
Subject: Re: [PATCH v2] ethdev: remove useless parameter in callback process
Date: Fri, 29 Dec 2017 14:29:21 +0100	[thread overview]
Message-ID: <19178544.sblBIO1mag@xps> (raw)
In-Reply-To: <20171228221013.1141-1-thomas@monjalon.net>

28/12/2017 23:10, Thomas Monjalon:
> The pointer to the user parameter of the callback registration is
> automatically pass to the callback function.
> There is no point to allow changing this user parameter by a caller.
> That's why this parameter is always set to NULL by PMDs and set only
> in ethdev layer before calling the callback function.
> 
> The history is that the user parameter was initially used
> by the callback implementation to pass some information
> between the application and the driver:
> 	c1ceaf3ad056 ("ethdev: add an argument to internal callback function")
> Then a new parameter has been added to leave the user parameter
> to its standard usage of context given at registration:
> 	d6af1a13d7a1 ("ethdev: add return values to callback process API")
> 
> The NULL parameter in the internal callback processing function
> is now removed. It makes clear that the callback parameter is user
> managed and opaque from a DPDK point of view.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> v2: add history explanation

This patch is now part of the patchset v3 for new ethdev notifications.

      reply	other threads:[~2017-12-29 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 22:09 [PATCH] ethdev: remove useless parameter in callback process Thomas Monjalon
2017-12-22  3:08 ` Ferruh Yigit
2017-12-28 21:54   ` Thomas Monjalon
2017-12-28 21:56     ` Thomas Monjalon
2017-12-28 22:10   ` [PATCH v2] " Thomas Monjalon
2017-12-29 13:29     ` Thomas Monjalon [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=19178544.sblBIO1mag@xps \
    --to=thomas@monjalon.net \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.