From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) by dpdk.org (Postfix) with ESMTP id C8745DE0 for ; Wed, 28 May 2014 02:45:26 +0200 (CEST) Received: by mail-la0-f42.google.com with SMTP id el20so6967934lab.29 for ; Tue, 27 May 2014 17:45:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=D2qbVehvlIOwoVKNsO7yaAhe7EcJYgPi6zCv/n36JWg=; b=RKiCcbW4z6+IKfpVTQPjG5McRwQwvk0wrIa8oZNOq/fTZFujXeX82gv+jSoY5SSwq9 Tq52E+nwQPWjLMB3vpFYxvivpWD5JWBiQq90Q3WgUQbFDPPo8peeBH1Djv/Z2ZRDt9cO 8akUheNwcL7rOZ90Q5UufJwATmwjO0AYpSqO0hB4au5TxWi0yI+W43YO5aEz1jba47b0 cBxgcxfZicq33cCCNzPgUC1RhKdumzn6VRifml1ie7rNSplRDsBdNShcKwTUxFbCiKZO wa9MsNTPohj7VBUOs5tnVaKInr2uqnnDor6Vn/vW5K3paK8biNPZpRfwZSYXWqcVE6Zp pTjg== X-Gm-Message-State: ALoCoQm9WRhMfAoG3MaFyRvAvj/k0oZg/DB12iq8BXvrB80KoxRUism8wJF1w17nNCuX8lKkCTjW MIME-Version: 1.0 X-Received: by 10.152.121.72 with SMTP id li8mr26106504lab.45.1401237937346; Tue, 27 May 2014 17:45:37 -0700 (PDT) Received: by 10.152.36.169 with HTTP; Tue, 27 May 2014 17:45:37 -0700 (PDT) In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891261B1BE888@IRSMSX102.ger.corp.intel.com> References: <20140527093457.7f5d9746@nehalam.linuxnetplumber.net> <3EB4FA525960D640B5BDFFD6A3D891261B1BE888@IRSMSX102.ger.corp.intel.com> Date: Tue, 27 May 2014 21:45:37 -0300 Message-ID: From: Ariel Rodriguez To: "Dumitrescu, Cristian" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Please any one who can help me with librte_sched X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2014 00:45:27 -0000 Thank you perfect explanation, i think im going to creating a new parallel rte_sched_port and change the reference with managment core updating the tx/sched core. So, what happens with the packets on the old reference if i just do rte_port_free on it, are them leaked? Is there a why to flush the rte_sched_port or maybe gets the packet total size somewhere?. Anyway the rcu algoritm fits ok in this aproach ... but maybe there is a way to flush the old reference port, and work from there with the recently created rte_sched_port .... Regars, Ariel. On Tue, May 27, 2014 at 3:31 PM, Dumitrescu, Cristian < cristian.dumitrescu@intel.com> wrote: > Hi Ariel, > > What's wrong with calling rte_sched_subport_config() and > rte_sched_pipe_config() during run-time? > > This assumes that: > > 1. Port initialization is done, which includes the following: > a) the number of subports, pipes per subport are fixed > b) the queues are all created and their size is fixed > c) the pipe profiles are defined > d) Basically the maximal data structures get created (maximum number of > supports, pipes and queues) with no run-time changes allowed, apart for the > bandwidth related parameters. Queues that do not receive packets are not > used now, they will be used as soon as they get packets. The > packets-to-queues mapping logic can change over time, as well as the level > of activity for different users/queues. > > 2. The CPU core calling the subport/pipe config functions is the same as > the core doing enque/dequeue for this port (for thread safety reasons). > a) As you say, the management core can send update requests to the core > running the scheduler, with the latter sampling the request queue regularly > and performing the updates. > > Regards, > Cristian > > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger > Sent: Tuesday, May 27, 2014 5:35 PM > To: Ariel Rodriguez > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] Please any one who can help me with librte_sched > > On Tue, 27 May 2014 10:33:02 -0300 > Ariel Rodriguez wrote: > > > Hello , this is my third mail , the previous mails have not been answered > > yet. > > > > I justo need someone explains to me how the librte_sched framework > behaves > > in a specific situation. > > > > I have a managment application , this connects with a ring with the tx > > core, when a user applies some configuration of the bandwith mangement , > > the tx core read the message in the ring parse the configuration in a > > rte_port_params struct , subport_params and pipe_params, then creates a > new > > rte_sched from scratch , and then changes the pointer of the current > > rte_sched_port currently doing scheduling and then the code execurte > > rte_sched_port_free() for the unreference (reference by temporal pointer) > > rte_sched_port . This is the only way i found for applying dinamic > > configuration or changes to the qos framework. > > So, with this, what happens with the packets attached to the old > > rte_sched_port while is deleted? are those lost packets inside the > > rte_sched_port generates memory leaks? how can i recover this packets _ > > just dequeing from the port scheduler? Where the port scheduler > indicates > > empty packets in the queu state? > > > > Is there a better way to achieve this kind of behaviour? i just need to > > update the rte_sched_port configuration dinamically, and i want to > change > > the current pipe configuration and sub port configuration also. > > > > Regards . > > If you need to do dynamic changes, I would recommend using an RCU type > algorithm where you exchange in new parameters and then cleanup/free > after a grace period. See http://lttng.org/urcu > > -------------------------------------------------------------- > Intel Shannon Limited > Registered in Ireland > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare > Registered Number: 308263 > Business address: Dromore House, East Park, Shannon, Co. Clare > > This e-mail and any attachments may contain confidential material for the > sole use of the intended recipient(s). Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > >