[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <864de21a-000b-5713-95e0-f71f536c567d@intel.com>
Date: Thu, 8 Dec 2022 10:17:01 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Saeed Mahameed <saeed@...nel.org>,
Tony Nguyen <anthony.l.nguyen@...el.com>
CC: <davem@...emloft.net>, <kuba@...nel.org>, <pabeni@...hat.com>,
<edumazet@...gle.com>, <netdev@...r.kernel.org>,
<richardcochran@...il.com>, <leon@...nel.org>,
Gurucharan G <gurucharanx.g@...el.com>
Subject: Re: [PATCH net-next v2 10/15] ice: disable Tx timestamps while link
is down
On 12/7/2022 3:46 PM, Saeed Mahameed wrote:
> On 07 Dec 13:09, Tony Nguyen wrote:
>> From: Jacob Keller <jacob.e.keller@...el.com>
>>
>> Introduce a new link_down field for the Tx tracker which indicates
>> whether
>> the link is down for a given port.
>>
>> Use this bit to prevent any Tx timestamp requests from starting while
>> link
> Can tx timestamp requests be generated in a context other than the xmit ndo
> ? how ?
>
> why not just use the same sync mechanisms we have for tx queues,
> carrier_down etc ..?
I can't find a record of a specific issue this fixed, and I checked and
can confirm that the netdev stack already checks netif_carrier_ok. Lets
just drop this from the series.
We'll have a new one with the bitmap_or change posted this afternoon and
this change dropped.
Thanks,
Jake
Powered by blists - more mailing lists