From: Arthas Kang <arthas.kang@gmail.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: Yongseok Koh <yskoh@mellanox.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] net/mlx4: add secondary process support
Date: Wed, 6 Mar 2019 11:06:34 +0800 [thread overview]
Message-ID: <CALK3x0=VpNBzfTH7aZhcZWfLGCEzFXtLAakbcRsC8iz1OvfMjw@mail.gmail.com> (raw)
In-Reply-To: <AM0PR0502MB3795D6559ECC2DFD6BB34359C3700@AM0PR0502MB3795.eurprd05.prod.outlook.com>
you can modify rdma-core libibverbs contain "MADV_DONTFORK" code.
On Sun, Mar 3, 2019 at 3:11 PM Shahaf Shuler <shahafs@mellanox.com> wrote:
> Same question regarding patchwork.
>
> Friday, March 1, 2019 3:27 AM, Yongseok Koh:
> > Subject: [RFC] net/mlx4: add secondary process support
> >
> > 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>
>
>
--
arthas kang
Email: arthas.kang@gmail.com
QQ: 27477657
prev parent reply other threads:[~2019-03-06 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 1:27 Yongseok Koh
2019-03-03 7:11 ` Shahaf Shuler
2019-03-06 3:06 ` Arthas Kang [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='CALK3x0=VpNBzfTH7aZhcZWfLGCEzFXtLAakbcRsC8iz1OvfMjw@mail.gmail.com' \
--to=arthas.kang@gmail.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--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).