From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "lihuisong (C)" <lihuisong@huawei.com>,
Joshua Washington <joshwash@google.com>,
Junfeng Guo <junfeng.guo@intel.com>,
Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/gve: add support for max_rx_bufsize
Date: Fri, 17 Nov 2023 10:59:35 +0000 [thread overview]
Message-ID: <9fd446aa-9a44-455e-9c4e-0b588b1f6977@amd.com> (raw)
In-Reply-To: <7733f1a7-1c70-1724-7d3d-13e798d30932@huawei.com>
On 11/17/2023 1:35 AM, lihuisong (C) wrote:
>
> 在 2023/11/17 6:16, Joshua Washington 写道:
>> The new max_rx_bufsize field in dev_info can be used to guide mbuf sizes
>> chosen by DPDK programs by ensuring that DPDK programs do not waste
>> memory by using an mbuf size too large for the maximum RX buffer size.
>> This patch adds support for this field in the GVE PMD.
>>
>> Signed-off-by: Joshua Washington <joshwash@google.com>
>> Reviewed-by: Rushil Gupta <rushilg@google.com>
>
> Reviewed-by: Huisong Li <lihuisong@huawei.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-11-17 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 22:16 Joshua Washington
2023-11-17 1:35 ` lihuisong (C)
2023-11-17 10:59 ` Ferruh Yigit [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=9fd446aa-9a44-455e-9c4e-0b588b1f6977@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=junfeng.guo@intel.com \
--cc=lihuisong@huawei.com \
--cc=rushilg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).