From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org,
Alexander Matushevsky <matua@amazon.com>
Subject: Re: [PATCH for-next v2 0/3] EFA updates 2020-02-25
Date: Fri, 28 Feb 2020 12:13:18 -0400 [thread overview]
Message-ID: <20200228161318.GA20969@ziepe.ca> (raw)
In-Reply-To: <20200225114010.21790-1-galpress@amazon.com>
On Tue, Feb 25, 2020 at 01:40:07PM +0200, Gal Pressman wrote:
> This series contains various updates to the device definitions handling
> and documentation.
>
> The last patch is based on a discussion that came up during the recent
> mmap machanism review on list:
> https://lore.kernel.org/linux-rdma/20190920133817.GB7095@ziepe.ca/
>
> We no longer delay the free_pages_exact call of mmaped DMA pages, as the
> pages won't be freed in case they are still referenced by the vma.
>
> Changelog -
> v1->v2: https://lore.kernel.org/linux-rdma/20200114085706.82229-1-galpress@amazon.com/
> * Use FIELD_GET and FIELD_PREP for EFA_GET/SET
> * Make sure to mask (clear) the field before ORing it with a new value
> * Clarify the commit message of the last patch
> * Reorder the cleanup in the last commit, entry removal now happens
> first
>
> Gal Pressman (3):
> RDMA/efa: Unified getters/setters for device structs bitmask access
> RDMA/efa: Properly document the interrupt mask register
> RDMA/efa: Do not delay freeing of DMA pages
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-02-28 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 11:40 [PATCH for-next v2 0/3] EFA updates 2020-02-25 Gal Pressman
2020-02-25 11:40 ` [PATCH for-next v2 1/3] RDMA/efa: Unified getters/setters for device structs bitmask access Gal Pressman
2020-02-25 11:40 ` [PATCH for-next v2 2/3] RDMA/efa: Properly document the interrupt mask register Gal Pressman
2020-02-25 11:40 ` [PATCH for-next v2 3/3] RDMA/efa: Do not delay freeing of DMA pages Gal Pressman
2020-02-28 16:13 ` Jason Gunthorpe [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=20200228161318.GA20969@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@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).