DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: dev@dpdk.org, gage.eads@intel.com, narender.vangati@intel.com,
	abhinandan.gujjar@intel.com
Subject: Re: [dpdk-dev] [PATCH] eventdev: add timestamping to received packets
Date: Tue, 20 Mar 2018 10:56:38 +0530	[thread overview]
Message-ID: <20180320052637.GA20302@jerin> (raw)
In-Reply-To: <20180312043446.GA19994@jerin>

-----Original Message-----
> Date: Mon, 12 Mar 2018 10:04:47 +0530
> From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> To: Nikhil Rao <nikhil.rao@intel.com>
> CC: dev@dpdk.org, gage.eads@intel.com, narender.vangati@intel.com,
>  abhinandan.gujjar@intel.com
> Subject: Re: [dpdk-dev] [PATCH] eventdev: add timestamping to received
>  packets
> User-Agent: Mutt/1.9.4 (2018-02-28)
> 
> -----Original Message-----
> > Date: Tue, 20 Feb 2018 06:30:54 -0500
> > From: Nikhil Rao <nikhil.rao@intel.com>
> > To: jerin.jacob@caviumnetworks.com
> > CC: dev@dpdk.org, gage.eads@intel.com, narender.vangati@intel.com,
> >  abhinandan.gujjar@intel.com, nikhil.rao@intel.com
> > Subject: [PATCH] eventdev: add timestamping to received packets
> > X-Mailer: git-send-email 1.8.3.1
> > 
> > Add timestamp to received packets before enqueuing to
> > event device if the timestamp is not already set. Adding
> > timestamp in the Rx adapter avoids additional latency due
> > to the event device.
> > 
> > Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> 
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

Applied to dpdk-next-eventdev/master. Thanks.

> 

      reply	other threads:[~2018-03-20  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 11:30 Nikhil Rao
2018-03-12  4:34 ` Jerin Jacob
2018-03-20  5:26   ` Jerin Jacob [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=20180320052637.GA20302@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=narender.vangati@intel.com \
    --cc=nikhil.rao@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).