DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Montorsi, Francesco" <fmontorsi@empirix.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Accurate timestamps in received packets
Date: Mon, 12 Oct 2015 12:25:28 +0000	[thread overview]
Message-ID: <5b03ff2e2449490981c6106d606745be@bilemail1.empirix.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20237E68D@IRSMSX103.ger.corp.intel.com>

Hi John, 
Thanks for your reply.

> -----Original Message-----
> From: Mcnamara, John [mailto:john.mcnamara@intel.com]
> AFAIK, timestamping of every packet isn't supported by ixgbe/i40e nics and I
> don't know about non-Intel nics. It was supported for some(?) igb nics and
> hence the patch you linked to. Also, there isn't any DPDK API to
> enable/disable it even if it is supported by the nic.

What a pity, that's a bad news for me. 
Another question in case you know: AFAIUI ixgbe/i40e devices receive packets in burst/sequences. What's the timeout for flushing the receive queue?
In other words, if I send a single packet to the PHY of the NIC, after how much time will the Intel network controller will stop waiting for further packets (to put in the same "burst") and send that single packet to the CPU?

Thanks,
Francesco

      reply	other threads:[~2015-10-12 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 15:30 Montorsi, Francesco
2015-10-10  4:52 ` Lu, Wenzhuo
2015-10-12  8:26   ` Montorsi, Francesco
2015-10-12  8:35     ` Mcnamara, John
2015-10-12 12:25       ` Montorsi, Francesco [this message]

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=5b03ff2e2449490981c6106d606745be@bilemail1.empirix.com \
    --to=fmontorsi@empirix.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=wenzhuo.lu@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).