linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: anish kumar <yesanishhere@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Leon Romanovsky" <leon@kernel.org>,
	"Jens Axboe" <axboe@kernel.dk>, "Jason Gunthorpe" <jgg@ziepe.ca>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
	"Christoph Hellwig" <hch@lst.de>,
	"Sagi Grimberg" <sagi@grimberg.me>,
	"Keith Busch" <kbusch@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Logan Gunthorpe" <logang@deltatee.com>,
	"Yishai Hadas" <yishaih@nvidia.com>,
	"Shameer Kolothum" <shameerali.kolothum.thodi@huawei.com>,
	"Kevin Tian" <kevin.tian@intel.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-rdma@vger.kernel.org,
	iommu@lists.linux.dev, linux-nvme@lists.infradead.org,
	linux-pci@vger.kernel.org, kvm@vger.kernel.org,
	linux-mm@kvack.org, "Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH v3 09/17] docs: core-api: document the IOVA-based API
Date: Sun, 10 Nov 2024 19:13:45 -0800	[thread overview]
Message-ID: <CABCoZhDpdU0cGu8Ru5Jj+YmnS07cO4k_nbOFT+HkdFkpVo1NYQ@mail.gmail.com> (raw)
In-Reply-To: <875xouv5lt.fsf@trenco.lwn.net>

On Sun, Nov 10, 2024 at 6:58 PM Jonathan Corbet <corbet@lwn.net> wrote:
>
> anish kumar <yesanishhere@gmail.com> writes:
>
> > On Sun, Nov 10, 2024 at 5:50 AM Leon Romanovsky <leon@kernel.org> wrote:
> >>
> >> From: Christoph Hellwig <hch@lst.de>
> >>
> >> Add an explanation of the newly added IOVA-based mapping API.
> >>
> >> Signed-off-by: Christoph Hellwig <hch@lst.de>
> >> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> >> ---
> >>  Documentation/core-api/dma-api.rst | 70 ++++++++++++++++++++++++++++++
> >>  1 file changed, 70 insertions(+)
> >>
> >> diff --git a/Documentation/core-api/dma-api.rst b/Documentation/core-api/dma-api.rst
> >> index 8e3cce3d0a23..61d6f4fe3d88 100644
> >> --- a/Documentation/core-api/dma-api.rst
> >> +++ b/Documentation/core-api/dma-api.rst
> >> @@ -530,6 +530,76 @@ routines, e.g.:::
> >>                 ....
> >>         }
> >>
> >> +Part Ie - IOVA-based DMA mappings
> >> +---------------------------------
> >> +
> >> +These APIs allow a very efficient mapping when using an IOMMU.  They are an
> >
> > "They" doesn't sound nice.
> >> +optional path that requires extra code and are only recommended for drivers
> >> +where DMA mapping performance, or the space usage for storing the DMA addresses
> >> +matter.  All the considerations from the previous section apply here as well.
> >
> > These APIs provide an efficient mapping when using an IOMMU. However, they
> > are optional and require additional code. They are recommended primarily for
> > drivers where performance in DMA mapping or the storage space for DMA
> > addresses are critical. All the considerations discussed in the previous section
> > also apply in this case.
> >
> > You can disregard this comment, as anyone reading this paragraph will
> > understand the intended message.
>
> I don't understand the comment, honestly.  You say "they" doesn't "sound
> nice", whatever that means, but your suggestion retains the "they"...?
>
> I'm all for reviews that improve our documentation, but it is
> *incredibly* easy to fall into the trivial bikeshed mode.  I've
> certainly done it myself.  The end result is less documentation as
> people decide, understandably, that it's not worth the pain.  Hopefully
> we can all try to do a bit less of that.
>
> FWIW, I think the paragraph is fine as written.

I completely agree, and that's why I suggested feeling free to disregard
the comment. When I read it, I felt it could be improved, but I
agree—there's no point in overanalyzing it.
>
> Thanks,
>
> jon


  reply	other threads:[~2024-11-11  3:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 13:46 [PATCH v3 00/17] Provide a new two step DMA mapping API Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 01/17] PCI/P2PDMA: Refactor the p2pdma mapping helpers Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 02/17] dma-mapping: move the PCI P2PDMA mapping helpers to pci-p2pdma.h Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 03/17] iommu: generalize the batched sync after map interface Leon Romanovsky
2024-11-18 14:46   ` Will Deacon
2024-11-10 13:46 ` [PATCH v3 04/17] dma-mapping: Add check if IOVA can be used Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 05/17] dma: Provide an interface to allow allocate IOVA Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 06/17] iommu/dma: Factor out a iommu_dma_map_swiotlb helper Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 07/17] dma-mapping: Implement link/unlink ranges API Leon Romanovsky
2024-11-18 14:59   ` Will Deacon
2024-11-18 18:55     ` Leon Romanovsky
2024-11-19  9:05       ` Will Deacon
2024-11-19 13:57         ` Leon Romanovsky
2024-11-19 17:30           ` Jason Gunthorpe
2024-11-10 13:46 ` [PATCH v3 08/17] dma-mapping: add a dma_need_unmap helper Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 09/17] docs: core-api: document the IOVA-based API Leon Romanovsky
2024-11-11  2:05   ` anish kumar
2024-11-11  2:58     ` Jonathan Corbet
2024-11-11  3:13       ` anish kumar [this message]
2024-11-10 13:46 ` [PATCH v3 10/17] mm/hmm: let users to tag specific PFN with DMA mapped bit Leon Romanovsky
2024-11-10 13:46 ` [PATCH v3 12/17] RDMA/umem: Store ODP access mask information in PFN Leon Romanovsky
2024-11-10 13:47 ` [PATCH v3 13/17] RDMA/core: Convert UMEM ODP DMA mapping to caching IOVA and page linkage Leon Romanovsky
2024-11-10 13:47 ` [PATCH v3 14/17] RDMA/umem: Separate implicit ODP initialization from explicit ODP Leon Romanovsky
2024-11-10 13:47 ` [PATCH v3 15/17] vfio/mlx5: Explicitly use number of pages instead of allocated length Leon Romanovsky
2024-11-10 13:47 ` [PATCH v3 16/17] vfio/mlx5: Rewrite create mkey flow to allow better code reuse Leon Romanovsky
2024-11-10 13:47 ` [PATCH v3 17/17] vfio/mlx5: Enable the DMA link API Leon Romanovsky
2024-11-10 15:02 ` [PATCH v3 00/17] Provide a new two step DMA mapping API Leon Romanovsky
2024-11-12  7:20 ` Leon Romanovsky
2024-11-14 13:30   ` Leon Romanovsky
2024-11-14 16:36     ` Christoph Hellwig
2024-11-14 16:48       ` Leon Romanovsky
2024-11-14 17:02         ` Christoph Hellwig

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=CABCoZhDpdU0cGu8Ru5Jj+YmnS07cO4k_nbOFT+HkdFkpVo1NYQ@mail.gmail.com \
    --to=yesanishhere@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=jglisse@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kbusch@kernel.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=m.szyprowski@samsung.com \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=sagi@grimberg.me \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=will@kernel.org \
    --cc=yishaih@nvidia.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