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 D6EF043FB8; Sun, 5 May 2024 18:03:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B1ABF402DE; Sun, 5 May 2024 18:03:07 +0200 (CEST) Received: from mail-pg1-f175.google.com (mail-pg1-f175.google.com [209.85.215.175]) by mails.dpdk.org (Postfix) with ESMTP id 1B1F04028C for ; Sun, 5 May 2024 18:03:05 +0200 (CEST) Received: by mail-pg1-f175.google.com with SMTP id 41be03b00d2f7-53fa455cd94so1004989a12.2 for ; Sun, 05 May 2024 09:03:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1714924985; x=1715529785; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=jA1sS3D18MfL72M/h3MnYkFoJlTH67UJFBnkPZdTVt8=; b=uaDRmRfWuJZeoNSCg6ciC3U6J5qytkZ9bcD2cgaOoBQqPXZOhgeudG90eiaQzzZFQg E9JT56nU6rrxh9Nb2QYWqMLo1o8SR4mtgShr95fzAhje7+QJKoTPHOuEN+Yby1asxa/e mewCdgVwFwKU4LvP/EaF3LtJX0iASkz/V+Kzy/EXAM52iYnHixS14yxsq5UX7GZBcF6o 31vnosM0Hc8XKWHfIp+LNEGZyWwlNIKi0iQJHYGsqnXwgMceGcKW68S1+wipfRhAZOu0 VOAeXvBPyL1TvRWVk5qUqXxwfRoSkoHbdF5iI+fs2pvz2r/XcF0cik3xC6/6oCap6b8F h9fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714924985; x=1715529785; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jA1sS3D18MfL72M/h3MnYkFoJlTH67UJFBnkPZdTVt8=; b=Zn29OkCUx0l79XU6TFqoIg6GKLMdZBSyjHdBktAqhcS1aQ/iM2tKu/CxQiTjzx5WiX nkx6cDtM6Oqg+rzZ22e3Ci6EnaNc81OUjDUKzi8w0Hp6BQSrRPz1MZsexiZ3OcViKb89 0VAODMpufeXFiXH878lQJi+tYY8QOgO/LS5LtleSkeddvsk+kuQmIv9OV4E+ZG2cxWfd TmQcHqq28wBZc5sSu5DThKJyay8oeKFZC6k15vMyb9GFA6vGPv2csE2jsOyyb+WDtktj Icg+i2uGJCtCGjnsu6FUvfmaH2Fxjm6Z1s8Te3xUFGB7dEhP4IgbgXFOjgtBPBTB2heN gnHQ== X-Forwarded-Encrypted: i=1; AJvYcCVvE4NlcrvXHEYgE6uWXRtS+ztd+y450gLpXBQLeUKG2PlRty3j7dWClN/CIpkw+8RfZOkuagDEC0NMI7Q= X-Gm-Message-State: AOJu0Yy5NiHokYHCQE8BlqunOl7HZJvEctMsuYRO3ZWLBm3+TYk9qAGz 4uAcvsNmJ4S3dcgN3D0euSmyNtorPtwGGaKq4oH+FQ5DDZMPAeQmVJqkR7JjIPw= X-Google-Smtp-Source: AGHT+IFKEis2oKt1APsHqlPhEScQEOqpIuOIHIJcP9w8C77T6T6sCAZiiw+tH7reNbX0ypL0CJiEYA== X-Received: by 2002:a05:6a00:c84:b0:6f3:ecdc:220e with SMTP id a4-20020a056a000c8400b006f3ecdc220emr8552947pfv.24.1714924984717; Sun, 05 May 2024 09:03:04 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id n21-20020a634d55000000b0060d95a83e43sm6335399pgl.18.2024.05.05.09.02.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 May 2024 09:03:00 -0700 (PDT) Date: Sun, 5 May 2024 09:02:56 -0700 From: Stephen Hemminger To: Fuji Nafiul Cc: users@dpdk.org, dev@dpdk.org Subject: Re: High packet capturing rate in DPDK enabled port Message-ID: <20240505090256.5e2d916f@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Sun, 5 May 2024 13:09:42 +0600 Fuji Nafiul wrote: > 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 The limitations of high speed packet capture is more about speed of writing to disk. Doing single write per packet is part of the problem. Getting higher performance requires faster SSD, and using ioring API. I do not believe that dpdkcap is really supporting writing at 10 Gbit/sec only that it can capture data on a 10 Gbit/sec device.