From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Chavent Subject: Re: [PATCH net-next v2] packet: tx timestamping on tpacket ring Date: Mon, 22 Apr 2013 10:19:40 +0200 Message-ID: <5174F29C.2030806@onera.fr> References: <1366408317-16432-1-git-send-email-willemb@google.com> <51728B32.4040200@redhat.com> <5173BB0F.90900@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Borkmann , netdev@vger.kernel.org, David Miller , Richard Cochran To: Willem de Bruijn Return-path: Received: from briaree.onecert.fr ([134.212.190.4]:47177 "EHLO briaree.onecert.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755746Ab3DVIYL (ORCPT ); Mon, 22 Apr 2013 04:24:11 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 04/21/2013 06:42 PM, Willem de Bruijn wrote: > Tx has the advantage that time sources can be chosen > per socket independent of all other sockets Sorry if my question is trivial. I understand that when we require rx timestamping, we need to ask to the device to timestamp all incoming packets since we don't know the path of the packet in advance. For tx timestamping, you seems to say that the request to timestamp the packet is contained in the skbuff and is done on a per packet basis ?