From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Pirko Subject: Re: [RFC net-next v1 1/1] net/sched: Introduce the taprio scheduler Date: Sat, 14 Jul 2018 08:45:05 +0200 Message-ID: <20180714064505.GA2821@nanopsycho.orion> References: <20180714000536.1008-1-vinicius.gomes@intel.com> <20180714000536.1008-2-vinicius.gomes@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org, jesus.sanchez-palencia@intel.com, tglx@linutronix.de, jan.altenberg@linutronix.de, henrik@austad.us, richardcochran@gmail.com, levi.pearson@harman.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com To: Vinicius Costa Gomes Return-path: Received: from mail-wm0-f67.google.com ([74.125.82.67]:38362 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725959AbeGNHEt (ORCPT ); Sat, 14 Jul 2018 03:04:49 -0400 Received: by mail-wm0-f67.google.com with SMTP id 69-v6so11106216wmf.3 for ; Fri, 13 Jul 2018 23:46:50 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20180714000536.1008-2-vinicius.gomes@intel.com> Sender: netdev-owner@vger.kernel.org List-ID: Sat, Jul 14, 2018 at 02:05:36AM CEST, vinicius.gomes@intel.com wrote: >This scheduler allows the network administrator to configure schedules >for classes of traffic, the configuration interface is similar to what >IEEE 802.1Qbv-2015 defines. > >Example configuration: > >$ tc qdisc add dev enp2s0 parent root handle 100 taprio \ > num_tc 3 \ > map 2 2 1 0 2 2 2 2 2 2 2 2 2 2 2 2 \ > queues 1@0 1@1 2@2 \ > sched-file ~/gates.sched \ > base-time 1000000 \ > clockid CLOCK_TAI > >This qdisc borrows a few concepts from mqprio and most the parameters >are similar to mqprio. The main difference is the 'sched-file' >parameter, one example of a schedule file would be: > >gates.sched Any particular reason this has to be in file and not on the cmdline?