From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: option for IEEE1588 Date: Tue, 12 Jul 2016 16:51:17 +0200 Message-ID: <2813600.ODDRtajQVC@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, christian.ehrhardt@canonical.com, pmatilai@redhat.com To: Wenzhuo Lu , Helin Zhang , Konstantin Ananyev , Jingjing Wu , Jing Chen Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 14B4C3239 for ; Tue, 12 Jul 2016 16:51:21 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id f126so130445419wma.1 for ; Tue, 12 Jul 2016 07:51:21 -0700 (PDT) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi all, We have a compile-time option for IEEE1588 feature. It means we must know wether the application will need it before compiling DPDK. Linux distributions must make this choice when packaging. Does it make sense to transform it into a runtime option? Is the performance drawback so big?