All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: jxgao@google.com, gregkh@linuxfoundation.org
Cc: saravanak@google.com, konrad.wilk@oracle.com, marcorr@google.com,
	linux-nvme@lists.infradead.org, iommu@lists.linux-foundation.org,
	kbusch@kernel.org, robin.murphy@arm.com
Subject: Re: preserve DMA offsets when using swiotlb v2
Date: Tue, 9 Feb 2021 09:41:56 +0100	[thread overview]
Message-ID: <20210209084156.GA32320@lst.de> (raw)
In-Reply-To: <20210207160327.2955490-1-hch@lst.de>

Sorry for being a little pushy, any chance we could get this reviewed
in time for the 5.12 merge window?

On Sun, Feb 07, 2021 at 05:03:18PM +0100, Christoph Hellwig wrote:
> Hi all,
> 
> this series make NVMe happy when running with swiotlb.  This caters
> towards to completely broken NVMe controllers that ignore the
> specification (hello to the biggest cloud provider on the planet!),
> to crappy SOC that have addressing limitations, or "secure"
> virtualization that force bounce buffering to enhance the user
> experience.  Or in other words, no one sane should hit it, but
> people do.
> 
> It is basically a respin of the
> 
>     "SWIOTLB: Preserve swiotlb map offset when needed."
> 
> series from Jianxiong Gao.  It complete rewrites the swiotlb part so that
> the offset really is preserved and not just the offset into the swiotlb
> slot, and to do so it grew half a dozen patches to refactor the swiotlb
> so that a mere mortal like me could actually understand it.
> 
> Changes since v2:
>  - cleanup nr_slots a little more
>  - fix a check in get_max_slots
>  - add a IO_TLB_SIZE define
>  - cleanup find_slots a little more
>  - fix the nvme patch to actually compile
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
---end quoted text---

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-02-09  8:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 16:03 preserve DMA offsets when using swiotlb v2 Christoph Hellwig
2021-02-07 16:03 ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 1/9] driver core: add a min_align_mask field to struct device_dma_parameters Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 2/9] swiotlb: add a IO_TLB_SIZE define Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 3/9] swiotlb: factor out an io_tlb_offset helper Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 4/9] swiotlb: factor out a nr_slots helper Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 5/9] swiotlb: clean up swiotlb_tbl_unmap_single Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 6/9] swiotlb: refactor swiotlb_tbl_map_single Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-22 19:05   ` Nicolas Saenz Julienne
2021-02-22 19:05     ` Nicolas Saenz Julienne
2021-02-22 19:29     ` Konrad Rzeszutek Wilk
2021-02-22 19:29       ` Konrad Rzeszutek Wilk
2021-02-23  7:25       ` Christoph Hellwig
2021-02-23  7:25         ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 7/9] swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 8/9] swiotlb: respect min_align_mask Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-07 16:03 ` [PATCH 9/9] nvme-pci: set min_align_mask Christoph Hellwig
2021-02-07 16:03   ` Christoph Hellwig
2021-02-09  8:41 ` Christoph Hellwig [this message]
2021-02-09  8:46   ` preserve DMA offsets when using swiotlb v2 Greg KH
2021-02-09  8:46     ` Greg KH
2021-02-09 19:49   ` Jianxiong Gao via iommu
2021-02-09 19:49     ` Jianxiong Gao
2021-02-19 18:13     ` Konrad Rzeszutek Wilk
2021-02-19 18:13       ` Konrad Rzeszutek Wilk

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=20210209084156.GA32320@lst.de \
    --to=hch@lst.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jxgao@google.com \
    --cc=kbusch@kernel.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=marcorr@google.com \
    --cc=robin.murphy@arm.com \
    --cc=saravanak@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.