[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <961edd82-23a4-41ee-a329-b7879ea1db54@nvidia.com>
Date: Fri, 8 Nov 2024 00:37:39 +0200
From: Chiara Meiohas <cmeiohas@...dia.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: dsahern@...il.com, leonro@...dia.com, linux-rdma@...r.kernel.org,
netdev@...r.kernel.org, jgg@...dia.com
Subject: Re: [PATCH v2 iproute2-next 0/5] Add RDMA monitor support
On 07/11/2024 18:24, Stephen Hemminger wrote:
> On Thu, 7 Nov 2024 10:02:43 +0200
> Chiara Meiohas <cmeioahs@...dia.com> wrote:
>
>> From: Chiara Meiohas <cmeiohas@...dia.com>
>>
>> This series adds support to a new command to monitor IB events
>> and expands the rdma-sys command to indicate whether this new
>> functionality is supported.
>> We've also included a fix for a typo in rdma-link man page.
>>
>> Command usage and examples are in the commits and man pages.
>>
>> These patches are complimentary to the kernel patches:
>> https://lore.kernel.org/linux-rdma/20240821051017.7730-1-michaelgur@nvidia.com/
>> https://lore.kernel.org/linux-rdma/093c978ef2766fd3ab4ff8798eeb68f2f11582f6.1730367038.git.leon@kernel.org/
> What happens if you run new iproute2 with these commands
> on an older kernel? What error is reported?
If we run "rdma monitor" on a kernel which doesn't support it:
it requires sudo privileges to run the command without failure,
then it will hang waiting to receive events.
The "rdma sys show" command will show "monitor off" as described
in the commit message.
Best regards,
Chiara
Powered by blists - more mailing lists