From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E2EF942DD8; Wed, 5 Jul 2023 14:56:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BB759406B5; Wed, 5 Jul 2023 14:56:39 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 5162C4021F for ; Wed, 5 Jul 2023 14:56:38 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 06C0E32008FF; Wed, 5 Jul 2023 08:56:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 05 Jul 2023 08:56:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1688561793; x=1688648193; bh=XbPWD+2yXW12aCyCQq262uunhFSTDrBiBvE a3kJX0d8=; b=sMyxJPa1Zu30p6EalMNG+ztrCf8mO+aUKunB1ZXyrnNFhEFXbDe v8RK3mtrMGPtCOL1sDOr6e/eO8CQyGQCkEIvTjXhWakT/VjTbO1GLGZx9g2F82XM PUeyK9GClY4ARndkzmJK84C39O/P/k0Uxnxvl/AfnkN2uRT37WjfOqNuk1Vm2xhu ZIG8qApVrFKidM9DcKyKmxOsdA2xthTIDB48gjEaFwhWYw3y/MZ+JecIDxgw1s7m QxB+9/N3gyPDEIPr617oCgol8dgZrtr8uYIRp/WKpo2zJ3KgfnrsS/iHcsbi15t+ CJ7pGHWri4Mi59wmMLbg7CpgFuOejbEqDhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1688561793; x=1688648193; bh=XbPWD+2yXW12aCyCQq262uunhFSTDrBiBvE a3kJX0d8=; b=PZDuxpkv7hdb48GE5cPwYB+MvX2+hyOmMXZ7B1BmvSxYz0iSnkI RW0cQepD+iZeIws1w3CqaHdqn0OZf1SKuASFhHkCCMDRMrUhKTEz5OpTeZI8Y0ye vO/uIyqWkS7TjAZbq5qM2GBKHBdNwH52bfXKRAhwxtrIL8Sh0XY602eN7wZM4gvi KbOdVjcLFTpSlhzp3+MN95KdFUHhw8034JgGDK3jfu+e7MX7HckcbnqP06q9Slo5 hQzzqzxpBvUubFY7VftvUIXclCyL5QzevFbiaXFdXGbsDH7L7g3KKjdnLQ0OYuyw zRVViW4bZgHzpc4c8TrXdvp1EVl00ZcfrDA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudejgddufecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Jul 2023 08:56:32 -0400 (EDT) From: Thomas Monjalon To: Nipun Gupta Cc: dev@dpdk.org, Ferruh.Yigit@amd.com, david.marchand@redhat.com, xuan.ding@intel.com, nikhil.agarwal@amd.com, xingguang.he@intel.com, weix.ling@intel.com, Nipun Gupta Subject: Re: [PATCH] doc: add information to update dma entry limit Date: Wed, 05 Jul 2023 14:56:29 +0200 Message-ID: <38378088.10thIPus4b@thomas> In-Reply-To: <20230705105307.5495-1-nipun.gupta@amd.com> References: <20230705105307.5495-1-nipun.gupta@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 05/07/2023 12:53, Nipun Gupta: > VFIO module provides configurable dma_entry_limit > parameter to store the DMA entries. By default this > is 64K and if we are using --no-huge, we shall need > to increase the value of dma_entry_limit. Add > commands in linux_gsg document to change the > dma_entry_limit. > > Signed-off-by: Nipun Gupta > --- > doc/guides/linux_gsg/linux_drivers.rst | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst > index 2cec1ebede..b729bb38a8 100644 > --- a/doc/guides/linux_gsg/linux_drivers.rst > +++ b/doc/guides/linux_gsg/linux_drivers.rst > @@ -180,6 +180,21 @@ VFIO module parameter ``dma_entry_limit`` with a default value of 64K. > When application is out of DMA entries, these limits need to be adjusted to > increase the allowed limit. > > +When ``no-huge`` parameter is used, the page size used is of smaller size of I would add "--" to have the full option "--no-huge". By the way, this is an "option" in the shell language :-) > +``4K`` or ``64K`` and we shall need to increase ``dma_entry_limit``. > +To update the ``dma_entry_limit``, ``vfio_iommu_type1`` has to be loaded with > +additional module parameter: > + > +.. code-block:: console > + > + modprobe vfio_iommu_type1 dma_entry_limit=512000 > + > +Alternatively, one can also change this value in an already loaded kernel module: > + > +.. code-block:: console > + > + echo 512000 > /sys/module/vfio_iommu_type1/parameters/dma_entry_limit That looks good, thank you.