Re: [PATCH 3/5] dma: Introduce dma_max_mapping_size()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Joerg Roedel <joro@xxxxxxxxxx>
Subject: Re: [PATCH 3/5] dma: Introduce dma_max_mapping_size()
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 23 Jan 2019 22:29:21 +0100
Cc: Jens Axboe <axboe@xxxxxxxxx>, jon.grimm@xxxxxxx, brijesh.singh@xxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, "Michael S . Tsirkin" <mst@xxxxxxxxxx>, jfehlig@xxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx, jroedel@xxxxxxx, Christoph Hellwig <hch@xxxxxx>
In-reply-to: <20190123163049.24863-4-joro@8bytes.org>
References: <20190123163049.24863-1-joro@8bytes.org> <20190123163049.24863-4-joro@8bytes.org>
User-agent: Mutt/1.5.17 (2007-11-01)

This looks ok, but could really use some documentation in
Documentation/DMA-API.txt.
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

References:
- [PATCH 0/5 v3] Fix virtio-blk issue with SWIOTLB
  - From: Joerg Roedel
- [PATCH 3/5] dma: Introduce dma_max_mapping_size()
  - From: Joerg Roedel

Prev by Date: Re: [PATCH 1/5] swiotlb: Introduce swiotlb_max_mapping_size()
Next by Date: Re: [Xen-devel] [RFC] virtio_ring: check dma_mem for xen_domain
Previous by thread: [PATCH 3/5] dma: Introduce dma_max_mapping_size()
Next by thread: [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size
Index(es):
- Date
- Thread

[Index of Archives] [KVM Development] [Libvirt Development] [Libvirt Users] [CentOS Virtualization] [Netdev] [Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]

Powered by Linux