netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Or Gerlitz <gerlitz.or@gmail.com>
To: Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>
Cc: David Miller <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Raghu Vatsavayi <raghu.vatsavayi@caviumnetworks.com>,
	Derek Chickles <derek.chickles@caviumnetworks.com>,
	Satanand Burla <satananda.burla@caviumnetworks.com>,
	Felix Manlunas <felix.manlunas@caviumnetworks.com>
Subject: Re: [PATCH net-next 4/5] liquidio VF timestamp
Date: Thu, 8 Dec 2016 23:09:39 +0200	[thread overview]
Message-ID: <CAJ3xEMg3RC74PEF-6_mF96Wj-dHWW6simspOpxkiObgXBr67KA@mail.gmail.com> (raw)
In-Reply-To: <1481230848-2393-5-git-send-email-rvatsavayi@caviumnetworks.com>

On Thu, Dec 8, 2016 at 11:00 PM, Raghu Vatsavayi
<rvatsavayi@caviumnetworks.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

  reply	other threads:[~2016-12-08 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 21:00 [PATCH net-next 0/5] liquidio VF offloads and stats Raghu Vatsavayi
2016-12-08 21:00 ` [PATCH net-next 1/5] liquidio VF vlan support Raghu Vatsavayi
2016-12-08 21:00 ` [PATCH net-next 2/5] liquidio VF vxlan Raghu Vatsavayi
2016-12-08 21:08   ` Or Gerlitz
2016-12-08 22:42     ` Vatsavayi, Raghu
2016-12-10 13:46       ` Or Gerlitz
2016-12-13  1:11         ` Felix Manlunas
2016-12-08 21:00 ` [PATCH net-next 3/5] liquidio VF ethtool stats Raghu Vatsavayi
2016-12-08 21:00 ` [PATCH net-next 4/5] liquidio VF timestamp Raghu Vatsavayi
2016-12-08 21:09   ` Or Gerlitz [this message]
2016-12-08 22:41     ` Chickles, Derek
2016-12-08 21:00 ` [PATCH net-next 5/5] liquidio VF error handling Raghu Vatsavayi
2016-12-08 23:17 ` [PATCH net-next 0/5] liquidio VF offloads and stats David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3xEMg3RC74PEF-6_mF96Wj-dHWW6simspOpxkiObgXBr67KA@mail.gmail.com \
    --to=gerlitz.or@gmail.com \
    --cc=davem@davemloft.net \
    --cc=derek.chickles@caviumnetworks.com \
    --cc=felix.manlunas@caviumnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=raghu.vatsavayi@caviumnetworks.com \
    --cc=rvatsavayi@caviumnetworks.com \
    --cc=satananda.burla@caviumnetworks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).