From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>, Kit Chow <kchow@gigaio.com>,
Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH 0/5] Support hot-unbind in IOAT
Date: Mon, 16 Dec 2019 12:01:15 -0700 [thread overview]
Message-ID: <20191216190120.21374-1-logang@deltatee.com> (raw)
Hey,
This patchset creates some common infrastructure which I will use in the
next version of the PLX driver. It adds a reference count to the
dma_device struct which is taken and released every time a channel
is allocated or freed. A call back is used to allow the driver to
free the underlying memory and do any final cleanup.
For a use-case, I've adjusted the ioat driver to properly support
hot-unbind. The driver was already pretty close as it already had
a shutdown state; so it mostly only required freeing the memory
correctly and calling ioat_shutdown at the correct time.
This patchset is based on v5.5-rc2 and a git branch is available here:
https://github.com/sbates130272/linux-p2pmem/ ioat-hot-unbind
Thanks,
Logan
--
Logan Gunthorpe (5):
dmaengine: Store module owner in dma_device struct
dmaengine: Call module_put() after device_free_chan_resources()
dmaengine: Move dma_channel_rebalance() infrastructure up in code
dmaengine: Add reference counting to dma_device struct
dmaengine: ioat: Support in-use unbind
drivers/dma/dmaengine.c | 352 +++++++++++++++++++++-----------------
drivers/dma/ioat/init.c | 38 ++--
include/linux/dmaengine.h | 10 +-
3 files changed, 233 insertions(+), 167 deletions(-)
--
2.20.1
next reply other threads:[~2019-12-16 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 19:01 Logan Gunthorpe [this message]
2019-12-16 19:01 ` [PATCH 1/5] dmaengine: Store module owner in dma_device struct Logan Gunthorpe
2019-12-16 19:01 ` [PATCH 2/5] dmaengine: Call module_put() after device_free_chan_resources() Logan Gunthorpe
2019-12-24 4:37 ` Vinod Koul
2019-12-16 19:01 ` [PATCH 3/5] dmaengine: Move dma_channel_rebalance() infrastructure up in code Logan Gunthorpe
2019-12-16 19:01 ` [PATCH 4/5] dmaengine: Add reference counting to dma_device struct Logan Gunthorpe
2019-12-16 19:01 ` [PATCH 5/5] dmaengine: ioat: Support in-use unbind Logan Gunthorpe
2019-12-17 16:33 ` Dave Jiang
2019-12-24 4:50 ` [PATCH 0/5] Support hot-unbind in IOAT Vinod Koul
2019-12-25 2:25 ` Logan Gunthorpe
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=20191216190120.21374-1-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kchow@gigaio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
/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).