From: William Tu <witu@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, jiri@nvidia.com, bodong@nvidia.com,
tariqt@nvidia.com, yossiku@nvidia.com, kuba@kernel.org
Subject: Re: [PATCH RFC iproute2] devlink: Add eswitch attr option for shared descriptors
Date: Wed, 28 Feb 2024 21:26:46 -0800 [thread overview]
Message-ID: <438e8df7-3deb-485a-8872-3e3b6974005f@nvidia.com> (raw)
In-Reply-To: <20240228083337.18bfc306@hermes.local>
On 2/28/24 8:33 AM, Stephen Hemminger wrote:
> External email: Use caution opening links or attachments
>
>
> On Wed, 28 Feb 2024 17:25:48 +0200
> William Tu <witu@nvidia.com> wrote:
>
>> Add two eswitch attrs: shrdesc_mode and shrdesc_count.
>> shrdesc_mode: to enable a sharing memory buffer for
>> representor's rx buffer, and shrdesc_count: to control the
>> number of buffers in this shared memory pool.
>>
>> An example use case:
>> $ devlink dev eswitch show pci/0000:08:00.0
>> pci/0000:08:00.0: mode legacy inline-mode none encap-mode basic \
>> shrdesc-mode none shrdesc-count 0
>> $ devlink dev eswitch set pci/0000:08:00.0 mode switchdev \
>> shrdesc-mode basic shrdesc-count 1024
>> $ devlink dev eswitch show pci/0000:08:00.0
>> pci/0000:08:00.0: mode switchdev inline-mode none encap-mode basic \
>> shrdesc-mode basic shrdesc-count 1024
>>
>> Signed-off-by: William Tu <witu@nvidia.com>
> This needs to target iproute2-next.
>
> Please update man page for devlink as well.
Hi Stephen,
Will fix it, thanks!
William
prev parent reply other threads:[~2024-02-29 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 15:25 [PATCH RFC iproute2] devlink: Add eswitch attr option for shared descriptors William Tu
2024-02-28 16:33 ` Stephen Hemminger
2024-02-29 5:26 ` William Tu [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=438e8df7-3deb-485a-8872-3e3b6974005f@nvidia.com \
--to=witu@nvidia.com \
--cc=bodong@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tariqt@nvidia.com \
--cc=yossiku@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.