netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Dong Zhu <bluezhudong@gmail.com>
Cc: Jacob Keller <Jacob.e.keller@intel.com>,
	Ben Hutchings <bhutchings@solarflare.com>,
	Matthew Vick <matthew.vick@intel.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Bruce Allan <bruce.w.allan@intel.com>,
	Carolyn Wyborny <carolyn.wyborny@intel.com>,
	Don Skidmore <donald.c.skidmore@intel.com>,
	Greg Rose <gregory.v.rose@intel.com>,
	Alex Duyck <alexander.h.duyck@intel.com>,
	John Ronciak <john.ronciak@intel.com>,
	Tushar Dave <tushar.n.dave@intel.com>,
	Akeem G Abodunrin <akeem.g.abodunrin@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	David Howells <dhowells@redhat.com>,
	Dave Jones <davej@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, e10
Subject: Re: [PATCH] igb: add a method to get the nic hw time stamping policy
Date: Tue, 14 May 2013 03:51:40 -0700	[thread overview]
Message-ID: <5192173C.1070808@intel.com> (raw)
In-Reply-To: <20130514095155.GO8399@zhudong.nay.redhat.com>

On 05/14/2013 02:51 AM, Dong Zhu wrote:
> Hi,
>
>> I modified this patch and added the method to igb_get_ts_info function.
>> For 82576 nic, through this method we can easily check which type of packets
>> are time stamped now, such as (HWTSTAMP_FILTER_PTP_V1_L4_SYNC and
>> HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ), then change or disable it up to your requests.
>> I think it is convenient.The origial GET_TS_INFO method can only show the device’s
>> time stamping capabilities which nics supported.
> Through this method we can easily check which type of packets are
> timestamped currently, it is useful because that we use the hwstamp_ctl
> set time stamping policy first then we could verify what type of packets
> does the nic timestamp and then do some other testing(regression) for each
> policy.No matter PTP is running or not we can make sure whether timestamp packets
> could cause other general network problems through viewing and setting the
> timestamp policy.

I'm trying to follow this thread, and Richard's question keeps coming up 
in my head, and you've failed to answer it yet.

What are you trying to fix/solve?

It sounds like what you're trying to add can already be retrieved 
through different mechanisms that already exist.

Please explain what you're trying to accomplish that doesn't already 
exist today, and why it's important.  If the facility exists already, 
then use that.  If it's not very usable, it can (maybe) be updated given 
what's deficient.  If it doesn't exist, then explaining why it needs to 
exist will help the case for the patches.

Just providing code doesn't help answer the question of what you're 
trying to do in the first place, and why what already exists isn't good 
enough.

Regards,
-PJ

  reply	other threads:[~2013-05-14 10:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11 14:02 [PATCH] igb: add a method to get the nic hw time stamping policy Dong Zhu
2013-05-11 15:31 ` Richard Cochran
2013-05-12 13:11   ` Dong Zhu
2013-05-11 16:51 ` Sergei Shtylyov
2013-05-12 14:25   ` Dong Zhu
2013-05-12 17:24     ` Richard Cochran
2013-05-13  2:12       ` Dong Zhu
2013-05-13  4:31         ` Richard Cochran
2013-05-13 10:07           ` Dong Zhu
2013-05-13 15:48             ` Vick, Matthew
2013-05-13 16:09               ` Ben Hutchings
2013-05-13 16:47             ` Keller, Jacob E
2013-05-14  9:51             ` Dong Zhu
2013-05-14 10:51               ` Peter P Waskiewicz Jr [this message]
2013-05-14 18:59               ` Keller, Jacob E

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=5192173C.1070808@intel.com \
    --to=peter.p.waskiewicz.jr@intel.com \
    --cc=Jacob.e.keller@intel.com \
    --cc=akeem.g.abodunrin@intel.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=bhutchings@solarflare.com \
    --cc=bluezhudong@gmail.com \
    --cc=bruce.w.allan@intel.com \
    --cc=carolyn.wyborny@intel.com \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=donald.c.skidmore@intel.com \
    --cc=gregory.v.rose@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.vick@intel.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=richardcochran@gmail.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=tglx@linutronix.de \
    --cc=tushar.n.dave@intel.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).