DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 2/3] net/mlx4: add external allocator for	Verbs object
Date: Tue, 26 Mar 2019 19:21:13 +0000	[thread overview]
Message-ID: <AM0PR0502MB379554B54D31CD6E56BF9578C35F0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190326192113.r7dTnmVwOM0DqS5ejLIZ8CNO-9GwjqETCRoyjZC4-YI@z> (raw)
In-Reply-To: <20190325191801.20841-3-yskoh@mellanox.com>

Monday, March 25, 2019 9:18 PM, Yongseok Koh:
> Subject: [dpdk-dev] [PATCH v2 2/3] net/mlx4: add external allocator for
> Verbs object
> 
> To support secondary process, the memory allocated by library such as
> completion rings (CQ) and buffer rings (WQ) must be manageable by EAL, in
> order to share it with secondary processes. With new changes in rdma-core
> and kernel driver, it is possible to provide an external allocator to the library
> layer for this purpose. All such resources will now be allocated within DPDK
> framework.
> 
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>

Acked-by: Shahaf Shuler <shahafs@mellanox.com>


  parent reply	other threads:[~2019-03-26 19:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  7:39 [dpdk-dev] [PATCH 0/3] net/mlx4: add secondary process support Yongseok Koh
2019-03-07  7:39 ` [dpdk-dev] [PATCH 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-03-07  7:39 ` [dpdk-dev] [PATCH 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-03-07  7:39 ` [dpdk-dev] [PATCH 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-03-25 19:17 ` [dpdk-dev] [PATCH v2 0/3] " Yongseok Koh
2019-03-25 19:17   ` Yongseok Koh
2019-03-25 19:17   ` [dpdk-dev] [PATCH v2 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-03-25 19:17     ` Yongseok Koh
2019-03-26 19:16     ` Shahaf Shuler
2019-03-26 19:16       ` Shahaf Shuler
2019-03-25 19:18   ` [dpdk-dev] [PATCH v2 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-03-25 19:18     ` Yongseok Koh
2019-03-26 19:21     ` Shahaf Shuler [this message]
2019-03-26 19:21       ` Shahaf Shuler
2019-03-25 19:18   ` [dpdk-dev] [PATCH v2 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-03-25 19:18     ` Yongseok Koh
2019-03-26 19:33     ` Shahaf Shuler
2019-03-26 19:33       ` Shahaf Shuler
2019-03-28 19:01       ` Yongseok Koh
2019-03-28 19:01         ` Yongseok Koh
2019-04-01 21:15 ` [dpdk-dev] [PATCH v3 0/3] " Yongseok Koh
2019-04-01 21:15   ` Yongseok Koh
2019-04-01 21:15   ` [dpdk-dev] [PATCH v3 1/3] net/mlx4: change device reference for secondary process Yongseok Koh
2019-04-01 21:15     ` Yongseok Koh
2019-04-01 21:15   ` [dpdk-dev] [PATCH v3 2/3] net/mlx4: add external allocator for Verbs object Yongseok Koh
2019-04-01 21:15     ` Yongseok Koh
2019-04-01 21:15   ` [dpdk-dev] [PATCH v3 3/3] net/mlx4: add secondary process support Yongseok Koh
2019-04-01 21:15     ` Yongseok Koh
2019-04-02  7:12   ` [dpdk-dev] [PATCH v3 0/3] " Shahaf Shuler
2019-04-02  7:12     ` Shahaf Shuler

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=AM0PR0502MB379554B54D31CD6E56BF9578C35F0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=yskoh@mellanox.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).