From: Yongseok Koh <yskoh@mellanox.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: dev <dev@dpdk.org>
Subject: [dpdk-dev] [RFC] net/mlx4: add secondary process support
Date: Fri, 1 Mar 2019 01:27:12 +0000 [thread overview]
Message-ID: <7F884229-3427-45BD-8C4D-F786AA1AFF03@mellanox.com> (raw)
In 19.05, mlx4 PMD will start to support secondary process. This will need new
rdma-core API and small fix in kernel driver, in order for Verbs to allow using
external (rte_malloc) memory allocator and remapping UAR space because secondary
process has to access device queues and UAR for Tx doorbell. Majority of changes
will come from mlx5 but mlx5_socket.c will not be imported. Instead, this will
be replaced with the new rte_mp_*() APIs. This is for secondary process to
acquire Verb's command file descriptor from primary process. The file descriptor
is required to remap UAR.
Patches are almost ready and I will be able to release v1 soon.
Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
next reply other threads:[~2019-03-01 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 1:27 Yongseok Koh [this message]
2019-03-03 7:11 ` Shahaf Shuler
2019-03-06 3:06 ` Arthas Kang
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=7F884229-3427-45BD-8C4D-F786AA1AFF03@mellanox.com \
--to=yskoh@mellanox.com \
--cc=dev@dpdk.org \
--cc=shahafs@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).