From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.digiweb.ie (smtp2.digiweb.ie [83.147.160.14]) by dpdk.org (Postfix) with ESMTP id 368C85A3E for ; Tue, 21 Apr 2015 12:50:55 +0200 (CEST) Received: from statler.emutex.com (unknown [92.51.199.138]) by smtp.digiweb.ie (Postfix) with ESMTP id ABFB3290027 for ; Tue, 21 Apr 2015 11:50:54 +0100 (IST) Received: from [90.162.149.153] (helo=[192.168.1.105]) by statler.emutex.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1YkVlW-0006kG-DU for dev@dpdk.org; Tue, 21 Apr 2015 11:50:54 +0100 Message-ID: <55362B8C.3030604@emutex.com> Date: Tue, 21 Apr 2015 11:50:52 +0100 From: Nicolas Pernas Maradei User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Saving packet timestamp when reading from pcap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 10:50:55 -0000 Hi Dor, What you are looking for seems straight forward to implement and it should not really affect the driver's performance at all. Even adding the full timestamp (seconds plus microseconds). However, I don't see too much people looking for that feature to make it to mainline. I could be wrong and it's not up to me to decide but I believe it wouldn't add too much value to the driver itself. It would make your testing easier but that's all. Maybe encapsulating the feature within #defines? If you were to read the packets from a pcap file and send them through a real NIC could you use the NIC's HW timestamp if supported? I'm not entirely sure about it (maybe someone else could provide more info about it) but it could solve your problem in a cleaner way. Nico.