[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220914203849.fn45bvuem2l3ppqq@sx1>
Date: Wed, 14 Sep 2022 21:38:49 +0100
From: Saeed Mahameed <saeedm@...dia.com>
To: sundeep subbaraya <sundeep.lkml@...il.com>
Cc: Saeed Mahameed <saeed@...nel.org>, liorna@...dia.com,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>, netdev@...r.kernel.org,
Tariq Toukan <tariqt@...dia.com>,
Raed Salem <raeds@...dia.com>, antoine.tenart@...tlin.com
Subject: Re: [PATCH net-next V2 07/17] net/mlx5: Add MACsec offload Tx
command support
On 14 Sep 20:09, sundeep subbaraya wrote:
>Hi Saeed and Lior,
>
>Your mdo_ops can fail in the commit phase and do not validate input
>params in the prepare phase.
>Is that okay? I am developing MACSEC offload driver for Marvell CN10K
It's ok since i think there is no reason to have the two steps system ! it
doesn't make any sense to me ! prepare and commit are invoked consecutively
one after the other for all mdo_ops and in every offload flow, with no extra
step in between! so it's totally redundant.
when i reviewed the series initially i was hesitant to check params
on prepare step but i didn't see any reason since commit can still fail in
the firmware anyways and there is nothing we can do about it !
so we've decide to keep all the flows in one context for better readability
and since the prepare/commit phases are confusing.
>and I had to write some clever code
>to honour that :). Please someone help me understand why two phase
>init was needed for offloading.
>
I don't know, let's ask the original author, Antoine ?
CC: Antoine Tenart <atenart@...nel.org>
Powered by blists - more mailing lists