[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN6PR07MB2932EC69BFB4F1D8B252F080F3840@BN6PR07MB2932.namprd07.prod.outlook.com>
Date: Thu, 8 Dec 2016 22:41:23 +0000
From: "Chickles, Derek" <Derek.Chickles@...ium.com>
To: Or Gerlitz <gerlitz.or@...il.com>,
"Vatsavayi, Raghu" <Raghu.Vatsavayi@...ium.com>
CC: David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
"Vatsavayi, Raghu" <Raghu.Vatsavayi@...ium.com>,
"Burla, Satananda" <Satananda.Burla@...ium.com>,
"Manlunas, Felix" <Felix.Manlunas@...ium.com>
Subject: RE: [PATCH net-next 4/5] liquidio VF timestamp
> -----Original Message-----
> From: Or Gerlitz [mailto:gerlitz.or@...il.com]
> Sent: Thursday, December 08, 2016 1:10 PM
> To: Vatsavayi, Raghu
> Cc: David Miller; Linux Netdev List; Vatsavayi, Raghu; Chickles, Derek; Burla,
> Satananda; Manlunas, Felix
> Subject: Re: [PATCH net-next 4/5] liquidio VF timestamp
>
> On Thu, Dec 8, 2016 at 11:00 PM, Raghu Vatsavayi
> <rvatsavayi@...iumnetworks.com> wrote:
> > Adds support for VF timestamp.
>
> same here, what's the use case? do you have per VF HW clocks to set?
> How it works if VF A does setup of X and VF B setup of Y
There's no support for adjusting per-VF clock skew and such in hardware,
but there is support for retrieving the hardware timestamp for Tx and Rx packets
on the VF. Applications can use this for their purposes.
Powered by blists - more mailing lists