netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Gal Pressman <galpress@amazon.com>
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	Yossi Leybovich <sleybo@amazon.com>,
	Alexander Matushevsky <matua@amazon.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH iproute2-next v2 0/2] Add copy-on-fork to get sys command
Date: Mon, 3 May 2021 08:44:43 -0600	[thread overview]
Message-ID: <bc278121-ed27-597b-cbc7-38129a58b7e1@gmail.com> (raw)
In-Reply-To: <20210429064803.58458-1-galpress@amazon.com>

On 4/29/21 12:48 AM, Gal Pressman wrote:
> This is the userspace part for the new copy-on-fork attribute added to
> the get sys netlink command.
> 
> The new attribute indicates that the kernel copies DMA pages on fork,
> hence fork support through madvise and MADV_DONTFORK is not needed.
> 
> Kernel series was merged:
> https://lore.kernel.org/linux-rdma/20210418121025.66849-1-galpress@amazon.com/
> 
> Changelog -
> v1->v2: https://lore.kernel.org/linux-rdma/20210428114231.96944-1-galpress@amazon.com/
> * Rebase kernel headers
> * Print attributes on the same line
> * Simplify if statement
> 
> Thanks
> 
> Gal Pressman (2):
>   rdma: update uapi headers
>   rdma: Add copy-on-fork to get sys command
> 
>  rdma/include/uapi/rdma/rdma_netlink.h |  3 +++
>  rdma/sys.c                            | 11 ++++++++++-
>  2 files changed, 13 insertions(+), 1 deletion(-)
> 

applied to iproute2-next

      parent reply	other threads:[~2021-05-03 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  6:48 [PATCH iproute2-next v2 0/2] Add copy-on-fork to get sys command Gal Pressman
2021-04-29  6:48 ` [PATCH iproute2-next v2 1/2] rdma: update uapi headers Gal Pressman
2021-04-29  7:13   ` Leon Romanovsky
2021-04-29  6:48 ` [PATCH iproute2-next v2 2/2] rdma: Add copy-on-fork to get sys command Gal Pressman
2021-04-29  7:12   ` Leon Romanovsky
2021-05-03 14:44 ` David Ahern [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=bc278121-ed27-597b-cbc7-38129a58b7e1@gmail.com \
    --to=dsahern@gmail.com \
    --cc=galpress@amazon.com \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matua@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=sleybo@amazon.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).