From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6B3B5A034F for ; Thu, 25 Feb 2021 19:20:15 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0BDCD406B4; Thu, 25 Feb 2021 19:20:14 +0100 (CET) Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) by mails.dpdk.org (Postfix) with ESMTP id D3CBA40692 for ; Thu, 25 Feb 2021 19:20:12 +0100 (CET) Received: by mail-oi1-f180.google.com with SMTP id x20so6984415oie.11 for ; Thu, 25 Feb 2021 10:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=bm5nFmBeAf8F6Kkv+Lr8oSwg0gVHficivsonu4zaUoI=; b=p0en3NVnLTmHYde1AbuqT5owrsUh4NQFgFa3gZFzv3MvvsqcIyP0PDottAqRUIyBVa c3AOASxRQaIQK6BpHmUbsMpPimg2ndp/7juSd0d1xAQh21vIG3JUcIHyZWuO4gwinxRs Fk5UUu4bUuF8jgeSvAjAiso1rWSSforWwEEvx5oxeF9iosb9qNnyMAwLHymzvsJr7QW3 /JwmK7xZaEejHlMAWXJENq1mCgTuMDaWn7v+qQ/bdIxIDj6NosSLgEbMeHgD44QQ81VI 2djPxhLv3jqSZ9uorelGbIcIrPnauWaa3+xpwBLuwByZlL4xl6GVboBz36qorlbvG/wk G97g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bm5nFmBeAf8F6Kkv+Lr8oSwg0gVHficivsonu4zaUoI=; b=CD4So7JRmtWasHKbNoQxEVKh2ifqOSCFzNNuJjl7GDov8WibDRxVEIsEnUF5bDoKE3 CEkhmfWJLFSI/J3G6nWOU3bhF43/WHu/qeAn2+e/FfnNl4H/FfdSeQBInCiet+hImpuv gwjCILCME8xdf7GrxIwBZa7eWvJ7cDP1wp/Ff2DtQLXJTgmAaCDWz+SWab9OhsanE49K 4y38WeoyTMGCKO7+4URDYRZ/QHJ2G8QzYrqnas5Pcdl4kLt6cJYM8EVPBwnscgpHO9Rm kUajFz7CBdA7DX645g1Ib+dBzFU1K81IhpI14ukW23r/61HMFxwFjQs6xH1EiATYExJP dirA== X-Gm-Message-State: AOAM532UqnoWMV480tyg8khOQnpgO+AmL26iGm0ZiDXylgCHOnh2ivqZ qFvgntQcmhOgdQiMtyqSwb4biVtL75eVdBDTACeKPdtpE9+T/A== X-Google-Smtp-Source: ABdhPJwpRsnkKhtLsqy71HCXOhpqY+gQB01Nvdc4Wl6tuUFg0rpGJcN6448GdUVAID2i7Z12ardCyP6E4E9E0HxZJOU= X-Received: by 2002:aca:4d06:: with SMTP id a6mr2947767oib.108.1614277211746; Thu, 25 Feb 2021 10:20:11 -0800 (PST) MIME-Version: 1.0 From: Douglas Fischer Date: Thu, 25 Feb 2021 15:20:01 -0300 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [dpdk-users] DPDK Limits by NIC - Choosing best routes X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Sorry if this is a recurrent topic in this list. I tried to search a bit on mail-archive... But I Didn't find what I guess is relevant. One of my major interests is using DPDK on software-based routers. I still don't understand very well the limitations of DPDK, but I'm pretty sure that it will mostly depend on the resources of the silicon on each card. Talking about Internet routing, the number of routes on FIB is a big matter= . But, allied to routing, other features like filtering/shaping/etc are also important. So, considering that FIB routes and Filtering resources compete by the same limited resources on NICs. I will also guess that would be reasonable to say that make senses do not push all the DFZ 900K routes to a NIC. (I'm so noobie on that that I even don't know if this would be possible.) So, if I won't be able to push all the routes to the NIC, makes sense that I choose the more often used routes. (Talking about normal ITP transit packets, usually, 90% of the packets are in between the same 20K routes.) And now comes the question: On the DPDK ecosystem, there is already something to deal with this choice of the best routes? Or it needs some extra daemon to deal with it? An extra question: Where can I confirm the amount of available DPDK resources on each NIC model? Thanks in advance! --=20 Douglas Fernando Fischer Eng=C2=BA de Controle e Automa=C3=A7=C3=A3o