From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ea0-f170.google.com (mail-ea0-f170.google.com [209.85.215.170]) by dpdk.org (Postfix) with ESMTP id 87E37156 for ; Thu, 28 Nov 2013 21:51:49 +0100 (CET) Received: by mail-ea0-f170.google.com with SMTP id k10so6326912eaj.1 for ; Thu, 28 Nov 2013 12:52:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=674B7axROsOfdhiUoK+xN7n6MVJXOBM1FAUVHPN6OlI=; b=gJ5xbsTbyDLx0oDXpoDh50zDBkNLjp5CVQiLJwHvg3Ll99OB/7WMqaI3btwD5LeYVg wveULmVuSJ+mwnTwLphv62aibA3oCFaETCO7zoSLmPCqEBqA4Piv6Tiafpnu7Zgmi02u fUqLHNU/dWyXt5JJOqJyNxkRL7xFZ5NJFH5f5b12c6t2k/ZBeLYensM+opOqI2I5B4qY Vg3FfuxGy8K2o7/SrzGqEm3ODfmVAbqAYPTqBLqYmKnrg0UUXqFcmUPBThmd9XTkO7mh BLOyD+QJ6gFnCOHnR2zBC3OftLHjfjn6/7jZZVTQC/P3kqWGpaclXi44pTKYnhu4mcmQ qCvw== X-Gm-Message-State: ALoCoQlqMkzGE8bWMBjkpCWAN3172nwi96acaMI+zqUViWU22L4pRox3dJCbDyszPI4e8VCk2oZE MIME-Version: 1.0 X-Received: by 10.15.23.206 with SMTP id h54mr50434787eeu.17.1385671968128; Thu, 28 Nov 2013 12:52:48 -0800 (PST) Received: by 10.14.89.4 with HTTP; Thu, 28 Nov 2013 12:52:47 -0800 (PST) X-Originating-IP: [200.69.240.117] Date: Thu, 28 Nov 2013 18:52:47 -0200 Message-ID: From: Ariel Rodriguez To: dev@dpdk.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] 4 Traffic classes per Pipe limitation 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: Thu, 28 Nov 2013 20:51:50 -0000 Hi, im working with the qos scheduler framework and i have a few questions. Why the 4 traffic classes per pipe limitation? . Im developing a deep packet inspection solution for a telecom company and i we need more than just 4 traffic classes per pipe. Im able to recognise almost all layer 7 applications, such as youtube, p2p , netflix , google-ads , etc, etc and i really need to map this type of flows in differents traffic classes. The idea is mark each flow depending on the provisioning information and assign that flows to different subport depending on the information given and assign a pipe with the subscriber contract rate, but we really need to have more than 4 traffic clases, because we want to control the bandwidth of different layer 7 protocols flows. At most we need 32 or 64 traffic classes per subscriber. I understand that in a given interval of time a subscriber dont use more than 4 protocols simultaneously , generally speaking , or 4 traffic classes in dpdk qos terminology, but the framework doesnt allow us to configure more traffic classes. Im looking the code of qos scheduler and im not seeing why this restriction. Is a performance problem, or a waste of resource problem? , maybe when the port grinder search for the active queues for each traffic class the delay of iterating over all pipes and each traffic class is too high. Cisco have a bandwidth managment solution that claims to control a million of subscribers simoultaneosly with 64 traffic classes per subscriber (pipes) and 4 queues per traffic classes (Cisco solution calls traffic clases as "Bandwith controller per service or BWC , a subscriber can have 64 BWC simoultaneasly). Its this posible? maybe this guys implements the bandwidth managment in hardware?. Anyway i really need this feature , but if the qos scheduller cannot scale to more than 4 traffic classes per pipe i would have to implement a custom packet scheduler from scratch and i really dont want to do that. Thanks for the patience, and sorry for my rusty english, im from Argentina. Best Regards. Ariel Horacio Rodriguez, Callis Technologies.