From: Wei Liu <wei.liu@kernel.org>
To: Michael Kelley <mhklinux@outlook.com>
Cc: Naman Jain <namjain@linux.microsoft.com>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Saurabh Sengar <ssengar@linux.microsoft.com>
Subject: Re: [PATCH v2] uio_hv_generic: Add a check for HV_NIC for send, receive buffers setup
Date: Wed, 8 Jan 2025 07:28:09 +0000 [thread overview]
Message-ID: <Z34pCVpGzhu_u8Pu@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <SN6PR02MB415727CA0BD7ECE337BD1E12D4122@SN6PR02MB4157.namprd02.prod.outlook.com>
On Wed, Jan 08, 2025 at 05:26:58AM +0000, Michael Kelley wrote:
> From: Naman Jain <namjain@linux.microsoft.com> Sent: Thursday, January 2, 2025 6:53 AM
> >
> > Receive and send buffer allocation was originally introduced to support
> > DPDK's networking use case. These buffer sizes were further increased to
> > meet DPDK performance requirements. However, these large buffers are
> > unnecessary for any other UIO use cases.
> > Restrict the allocation of receive and send buffers only for HV_NIC device
> > type, saving 47 MB of memory per device.
> >
> > While at it, fix some of the syntax related issues in the touched code
> > which are reported by "--strict" option of checkpatch.
> >
> > Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
[...]
>
> Reviewed-by: Michael Kelley <mhklinux@outlook.com>
Applied to hyperv-next. Thanks.
prev parent reply other threads:[~2025-01-08 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 14:52 [PATCH v2] uio_hv_generic: Add a check for HV_NIC for send, receive buffers setup Naman Jain
2025-01-08 5:26 ` Michael Kelley
2025-01-08 7:28 ` Wei Liu [this message]
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=Z34pCVpGzhu_u8Pu@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=ssengar@linux.microsoft.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