[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4335a01-a98b-573c-9747-b4039188340c@gmail.com>
Date: Fri, 25 Aug 2017 12:51:31 -0700
From: David Ahern <dsahern@...il.com>
To: Arkadi Sharshevsky <arkadis@...lanox.com>,
Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, idosch@...lanox.com, mlxsw@...lanox.com
Subject: Re: [patch net-next 11/12] mlxsw: spectrum_dpipe: Add support for
IPv4 host table dump
On 8/25/17 2:26 AM, Arkadi Sharshevsky wrote:
>
>
> On 08/24/2017 10:26 PM, David Ahern wrote:
>> On 8/23/17 11:40 PM, Jiri Pirko wrote:
>>> +static int
>>> +mlxsw_sp_dpipe_table_host_entries_get(struct mlxsw_sp *mlxsw_sp,
>>> + struct devlink_dpipe_entry *entry,
>>> + bool counters_enabled,
>>> + struct devlink_dpipe_dump_ctx *dump_ctx,
>>> + int type)
>>> +{
>>> + int rif_neigh_count = 0;
>>> + int rif_neigh_skip = 0;
>>> + int neigh_count = 0;
>>> + int rif_count;
>>> + int i, j;
>>> + int err;
>>> +
>>> + rtnl_lock();
>>
>> Why does a h/w driver dumping its tables need the rtnl lock?
>>
>
> This table represents the hw IPv4 arp table, and the
> driver depends on rtnl to be held.
>
Meaning mlxsw does not have its own locks protecting data structures --
e.g., rif adds and deletes, so it is relying on rtnl?
Also, this dpipe capability seems to be just dumping data structures
maintained by the driver. ie., you can compare the mlxsw view of
networking state to IPv4 and IPv6 level tables. Any plans to offer a
command that reads data from the h/w and passes that back to the user?
i.e, a command to compare kernel tables to h/w state?
Powered by blists - more mailing lists