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 C2C9643FAC; Sun, 5 May 2024 09:09:56 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 38C3E4028C; Sun, 5 May 2024 09:09:56 +0200 (CEST) Received: from mail-pf1-f172.google.com (mail-pf1-f172.google.com [209.85.210.172]) by mails.dpdk.org (Postfix) with ESMTP id 18BEE4025D; Sun, 5 May 2024 09:09:55 +0200 (CEST) Received: by mail-pf1-f172.google.com with SMTP id d2e1a72fcca58-6edc61d0ff6so943092b3a.2; Sun, 05 May 2024 00:09:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714892994; x=1715497794; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=U254bK61jzQJWyqghXMe7+DRo05cFNImwC/LleJD+wI=; b=PoSbYuQqKkxAYrE+FlBCdxp6ocCCFTynI6HfgOYi+1raTjDAHwB7ZycsBF+RdugDp2 cW5Iab+38uy28HNjyGbe8HJQzz+R/gVqCCefbkLS6LZYUHFx7sYYv73nFnsFu4oYrQgV M8ElZm10tOnqoToZPhSJpKGIxyt3Suyxkfo/XvARPIMlwmu+XYslJc5zwRt1+NXSGq3r Q95fyaU2vlVWMv88Lz0ISYJK2xtGjsnSVSAV4Sa7iXS1P0LwCyFNt0iMi+K76Y0FIq48 Dy4aZLXzKXHFM3Y/YilJ1iLAsL1RNCP0fudmAjZZPIAJJzPOlhvBh3ljWth33vCIEokR nj0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714892994; x=1715497794; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=U254bK61jzQJWyqghXMe7+DRo05cFNImwC/LleJD+wI=; b=ZlLq2i3KLAzNobwH8tnsH3JOTh7X6gZ9+uJVxoA5Yb0+NEmmf1MU4qTxl7lF5po2MM pre/PNQOELu1k3ynOZ9fr1KIWrbH+rjkoBwgGwlABKS6Ggyb/4gI2WaktzQLIJTMpCFC uI5zOJThTQSrJbuHX9kW8dDQChjGWe02oODJlFFacTpFDw2n7kpObHG9kG3ijNt6h4ag jfZLbHdoerSTjXB0M2vSaBTjaT3AzjGOboAB1TEIB+Imby7RWnu4BcWwycsxpZOdtrMd PAaFlhFMhHH7AYZqs542e8sW+4P7+Xe7QWryhq3S2c11N/LiUryAeXY81+wKyDOy+qft m0Dw== X-Forwarded-Encrypted: i=1; AJvYcCWdmcn6+TRF08ki3CPy9L6wubqBty9ah72d1H4P5WZFg6YBYWcLN2Qlqd6pdgsVByoiHbUqdk1gkK1s/CU= X-Gm-Message-State: AOJu0Yx1nOA5WPFAksrvtmU9NJieuYcZSqCVC6VA+/W0ZOnE4vr6fHIi rQ6SJ9P9OdZcxFQhFCJYAmiTfWFTwqi0bQp8GrnMlgckN4ndHZIyAssbyNHK7nyDpPC28Wj/EZb idGHjYauUMNH2XVjcUaA/CJE/jtTpLJP3 X-Google-Smtp-Source: AGHT+IHvNSz6HHLQ4k+q5gJXZesIJEpI+orq2HfEj2QdiPWlmvy6IYn8ZSLN7nBkrC9+IQtHSAuUwwRBQJPQ+L8uuTg= X-Received: by 2002:a05:6a21:610:b0:1af:b0b6:a35f with SMTP id ll16-20020a056a21061000b001afb0b6a35fmr47937pzb.2.1714892993458; Sun, 05 May 2024 00:09:53 -0700 (PDT) MIME-Version: 1.0 From: Fuji Nafiul Date: Sun, 5 May 2024 13:09:42 +0600 Message-ID: Subject: High packet capturing rate in DPDK enabled port To: users@dpdk.org, dev@dpdk.org Content-Type: multipart/alternative; boundary="000000000000b3f8660617afa3e2" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --000000000000b3f8660617afa3e2 Content-Type: text/plain; charset="UTF-8" I have a DPDK-enabled port (Linux server) that serves around 5,000-50,000 concurrent calls, per packet size of 80 bytes to 200 bytes. so in peak time, I require packet capture + file writing speed of around 1GByte/s or 8 Gbit/sec (at least 0.5Gbyte/s is expected). dpdk official packet capture example project "dpdk-dumpcap"'s documentation says it has a capability of around 10MByte/s which is far less than required. I implemented a simple packet capture and pcap writing code which was able to dump around 5000-7000 concurrent call data where I used 1 core and 1 single ring of size 4096, and this was all integrated into actual media code (didn't use librte_pdump, simply copied to separate rte_ring after capturing through rte_eth_rx_burst() and before sending through rte_eth_tx_burst() ). I know I can launch this multiple cores and with multiple rings and so on but is there any current project which already does this? I found a third-party project named "dpdkcap" which says it can support up to 10Gbit/s. Has anyone used it and what's the review? Or, should I modify the "dpdk-dumpcap" project to my need to implement multicore and multi-ring support so I can extend the capability? Thanks in advance --000000000000b3f8660617afa3e2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have a DPDK-enabled=C2=A0port (Linux server) that serves= around 5,000-50,000 concurrent calls, per packet size of 80 bytes=C2=A0to = 200 bytes. so in peak time, I require packet capture=C2=A0+ file writing speed of around 1GByt= e/s or 8 Gbit/sec (at least=C2=A00.5Gbyte/s is expected). dpdk official pac= ket capture example project "dpdk-dumpcap"'s documentation sa= ys it has a capability of around 10MByte/s which is far less than required.= I implemented a simple packet capture and pcap writing code which was able= to dump around=C2=A05000-7000 concurrent call data where I used 1 core and= 1 single ring of size 4096, and this was all integrated into actual media = code (didn't use librte_pdump, simply copied to separate rte_ring after= capturing through rte_eth_rx_burst() and before sending through rte_eth_tx= _burst() ). I know I can launch this multiple cores and with multiple rings= and so on but is there any current project which already does this?=C2=A0<= br>
I found a third-party project named "dpdkcap" which says i= t can support up to 10Gbit/s. Has anyone used it and what's the review?=

Or, should I modify=C2=A0the "dpdk-dumpcap" project to m= y need=C2=A0to implement=C2=A0multicore=C2=A0and multi-ring support so I ca= n extend the capability?
Thanks in advance
--000000000000b3f8660617afa3e2--