DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>, dev@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 18.05-RC3 v2] mem: add argument to mem event callbacks
Date: Fri, 4 May 2018 09:35:26 +0200	[thread overview]
Message-ID: <8708c256-8154-9552-1442-3f6a7baea6d1@redhat.com> (raw)
In-Reply-To: <e9278f20c6d41dffd0c8d7f798ddab88e911827b.1525336066.git.anatoly.burakov@intel.com>

Hi Anatoly,

On 05/03/2018 10:28 AM, Anatoly Burakov wrote:
> It may be useful to pass arbitrary data to the callback (such
> as device pointers), so add this to the mem event callback API.
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Suggested-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> 
> Notes:
>      v2:
>      - Fixed compile issue in VFIO
>      
>      This is needed to fix virtio-user issues under new memory model,
>      in order to avoid iterating over all virtio devices on callback.
> 
>   drivers/bus/fslmc/fslmc_vfio.c              |  5 +++--
>   lib/librte_eal/common/eal_common_memalloc.c | 26 +++++++++++++++-----------
>   lib/librte_eal/common/eal_common_memory.c   |  9 +++++----
>   lib/librte_eal/common/eal_memalloc.h        |  4 ++--
>   lib/librte_eal/common/include/rte_memory.h  | 13 ++++++++++---
>   lib/librte_eal/linuxapp/eal/eal_vfio.c      |  8 +++++---
>   6 files changed, 40 insertions(+), 25 deletions(-)

Thanks for doing this change, FWIW:
Tested-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Regards,
Maxime

  reply	other threads:[~2018-05-04  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  7:47 [dpdk-dev] [PATCH 18.05-RC3] " Anatoly Burakov
2018-05-03  7:51 ` Maxime Coquelin
2018-05-03  8:10   ` Burakov, Anatoly
2018-05-03  8:28 ` [dpdk-dev] [PATCH 18.05-RC3 v2] " Anatoly Burakov
2018-05-04  7:35   ` Maxime Coquelin [this message]
2018-05-08 20:18     ` 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=8708c256-8154-9552-1442-3f6a7baea6d1@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=shreyansh.jain@nxp.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).