From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinicius Costa Gomes Subject: Re: [RFC net-next v1 1/1] net/sched: Introduce the taprio scheduler Date: Mon, 16 Jul 2018 10:13:23 -0700 Message-ID: <87va9fgl3g.fsf@intel.com> References: <20180714000536.1008-1-vinicius.gomes@intel.com> <20180714000536.1008-2-vinicius.gomes@intel.com> <20180714064505.GA2821@nanopsycho.orion> Mime-Version: 1.0 Content-Type: text/plain 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: Jiri Pirko Return-path: Received: from mga11.intel.com ([192.55.52.93]:34001 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727652AbeGPRlp (ORCPT ); Mon, 16 Jul 2018 13:41:45 -0400 In-Reply-To: <20180714064505.GA2821@nanopsycho.orion> Sender: netdev-owner@vger.kernel.org List-ID: Hi Jiri, Jiri Pirko writes: [...] >> >>gates.sched > > Any particular reason this has to be in file and not on the cmdline? The idea here was to keep longer schedules more manageable. And during testing I found it more ergonomic to have a file. It also has the advantage that the file can be reused by other tools, dump-classifier (awful name, I admit), included in that github gist, is one example, it uses the schedule (and some more information) to calculate which packets would fall outside their "windows" in a pcap dump. Anyway, if there are use cases that having the schedule in the command line helps, I would be happy to add it. Cheers,