From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f194.google.com (mail-wr0-f194.google.com [209.85.128.194]) by dpdk.org (Postfix) with ESMTP id 5A2A42C23 for ; Tue, 28 Feb 2017 10:25:05 +0100 (CET) Received: by mail-wr0-f194.google.com with SMTP id g10so829435wrg.0 for ; Tue, 28 Feb 2017 01:25:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zlRCmn0/xvMZnugsoC9pHD5S91wyF/ACdsp1xMeVa1U=; b=e9oQXcl2l8MEOJABL3YjnEO4c1MnnVt2TJluNRROs3vrcSDjca7VKwCzbX+XKOzR29 OPrl5MW16UO7MDM72zPWxGcRkxI67uZroUXGNqXdg6vUPX9KJMwniAn3L90oRYPBWyJC 6txxWXnqlWesR/PHspxIKUR7D9v6ApQsvQJK7ix8Nt1PJuwh0ydKV2s3SIY/SWGwNLU3 b9ESjqwdFvG9ByzqjQQzZQURfWytvtxBclxV1WTXO3VtVbHGaGSbDNAPGyeYY3EEc8U1 0h29C085D4bSQo8fUyET/uAQEfFO0Qh8pbiaX/g1nqYuJwIHzHpMfRHYPOCjaVBJv4jm Cnzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zlRCmn0/xvMZnugsoC9pHD5S91wyF/ACdsp1xMeVa1U=; b=ifcrxPBoHzCEOoOq9CzzTNwiL9NMGqYv9Y4am1y5gmNRiwiZ2ZPOu77U63kL5ID10Q t7/wcPHHUAq7uwsgnhpaiTl8wJl1Giffr5gwvRKY9g/t6ZNuK0gDfOspRaY02nOMNQZT vdb6sIsxa6qY4+NRJQsP/4kWhHT8UnN76ZkO/8K4Uh44nMYuAPY3E6dk52ku8RcERNn7 qM6EfNdzhd2rgQCto6Mx5Z/ysbcTB3VMggKaLwmhZM7X90Xee3QB8/dyTo3pcFEnx5Tu hnXxeKDvsW7EwPaDUrktJbXlYp0ghEH+XOF7C0BKxSHdmJaDg9qsuVKpd3t0uFxFRJa8 McEg== X-Gm-Message-State: AMke39m+LMGQZ+dULo7iuA4tPzYjdAvv7EQ1XGc0FFwva377iFMR20HjtFQulk0zhUBGToTLZC/eyLvLeKYIJA== X-Received: by 10.223.132.166 with SMTP id 35mr1247576wrg.122.1488273904873; Tue, 28 Feb 2017 01:25:04 -0800 (PST) MIME-Version: 1.0 Sender: jblunck@gmail.com Received: by 10.28.211.20 with HTTP; Tue, 28 Feb 2017 01:25:04 -0800 (PST) In-Reply-To: <2601191342CEEE43887BDE71AB9772583F11E992@irsmsx105.ger.corp.intel.com> References: <1485271173-13408-1-git-send-email-olivier.matz@6wind.com> <2601191342CEEE43887BDE71AB9772583F111A29@irsmsx105.ger.corp.intel.com> <20170216144807.7add2c71@platinum> <20170217115153.0afeb061@platinum> <20170217151708.20bf4a49@platinum> <20170221105400.2eba4747@glumotte.dev.6wind.com> <20170221163808.GA213576@bricha3-MOBL3.ger.corp.intel.com> <2601191342CEEE43887BDE71AB9772583F11B4CC@irsmsx105.ger.corp.intel.com> <2601191342CEEE43887BDE71AB9772583F11B633@irsmsx105.ger.corp.intel.com> <20170224150053.279e718d@platinum> <2601191342CEEE43887BDE71AB9772583F11E992@irsmsx105.ger.corp.intel.com> From: Jan Blunck Date: Tue, 28 Feb 2017 10:25:04 +0100 X-Google-Sender-Auth: g5KWlWEJjeNgmvRdJuLXdmITq3g Message-ID: To: "Ananyev, Konstantin" Cc: Olivier Matz , "Richardson, Bruce" , "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 Subject: Re: [dpdk-dev] [RFC 0/8] mbuf: structure reorganization X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 09:25:05 -0000 On Tue, Feb 28, 2017 at 10:05 AM, Ananyev, Konstantin wrote: >> > >> > In both cases, we would need a conversion code (maybe in a library) if >> > the application wants to work with timestamps from several sources. The >> > second solution removes the normalization code in the PMD when not >> > needed, it is probably better. >> >> I agree. > > One question - does that mean that application would need to > keep a track from what PMD each particular packet came to do the normalization? Yes. You usually do this based on mbuf->port.