From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A4182A05A1 for ; Wed, 22 Apr 2020 05:50:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EF6321C204; Wed, 22 Apr 2020 05:50:09 +0200 (CEST) Received: from mail-pl1-f169.google.com (mail-pl1-f169.google.com [209.85.214.169]) by dpdk.org (Postfix) with ESMTP id 5EF321C114 for ; Wed, 22 Apr 2020 05:50:08 +0200 (CEST) Received: by mail-pl1-f169.google.com with SMTP id s10so405811plr.1 for ; Tue, 21 Apr 2020 20:50:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=xfPhbnRYOnXZTm1B4NLP+wX5bnkueYa8PG4IL+9jXRQ=; b=Yp9JXRLXfE0KmtOUb967M3qJtrRAEQS0sE5Y1nzGL6CWIpbwjaVveHtQDP1Xqu9pXB jjePpOJhNDTdpVEhGP5wnpWZDFsW7lXgrv6OodaIW2YKDWDSDfNxNUnh8rolQEiynStE mdcM/iSFBS0xN82WQo/5dWxB7Skebuli1Wv97CxJ26KmkC4lDRsT0OX1WjC1LOmjXE6z Vayl7LsS8WYdSe9ClocH7cBahRgw11FAaAwC0LMpfSDU1gpj3J5HhCp6O2DjwqEiS9sE X5OZFUNhW8/m+HFUphSjOZ2R6pz7CcNlXrRe7zlsAD3nWoy1BRyqFtXMhtwzjIxo1PvZ oJVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=xfPhbnRYOnXZTm1B4NLP+wX5bnkueYa8PG4IL+9jXRQ=; b=QFZ9VdHsasv8U7sFfynCEE3kAVHxL0f/rb27eXZGCauxkq3zRhusZwv2PqcOiHcRmS RVwQVSblMLzk0cMv4FeTBawhanu5p4DcjEeVPpa1R8dgH6yschS+XCmhf7mbsAVZ521V BF2vfegjAaUil7+huFstgZdkc+YchVyHzFul+m+D2yIVpvIq486jg1+vAhrDy31LoyaW kYHHDJC3BKJ2O4ATLEthEBHpwZdE933OAEZbh6JFyAOKAEHcrcHZa5MXzgXcWFGI/aQF AVV7eGDnteG7gdeEl800j/DSk3Jsv7Mq+bYH9159U2mxYsw4TFgOHw0TEV3o16iuNMzc HSjw== X-Gm-Message-State: AGi0PuYak3ULitNADJe1s+LZOR8V7wZnL69oCmsfCegYKDA0+kaKQddp b+XNrpDiY8k7QNw7zgpVYnUArwuR5Xs= X-Google-Smtp-Source: APiQypLcAQY6WUijtD9qejFYSgPiS/+OPB5pz6SwByWzTjNcsn3uSaGO00LYsrYMEy7Bti004J1DCw== X-Received: by 2002:a17:90b:93:: with SMTP id bb19mr9542438pjb.134.1587527407134; Tue, 21 Apr 2020 20:50:07 -0700 (PDT) Received: from ?IPv6:2406:3003:2005:20c2:65e7:e562:35f:e964? ([2406:3003:2005:20c2:65e7:e562:35f:e964]) by smtp.gmail.com with ESMTPSA id y6sm3888732pjw.23.2020.04.21.20.50.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Apr 2020 20:50:06 -0700 (PDT) To: users@dpdk.org From: Alireza Sanaee Message-ID: <7103100c-ff28-2ff8-deef-37b9a1877ae6@gmail.com> Date: Wed, 22 Apr 2020 11:50:04 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: [dpdk-users] Capturing Pause Frames in DPDK Applications X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 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" Dear all, I'm wondering that if there is any chances to pass pause frames through a NIC and receive it in the DPDK application? Is there any ideas to practically make this modification? I have read that Pause Frames are being consumed at ASIC level so it would not be possible to pass the frame to CPU. In that case, I'm just thinking of creating an artificial pause frame on arrival of a real Ethernet pause frame and push the artificial one to software, it might be crazy though but still capturing arrival event of an Ethernet pause frame remains a challenge. In a DPDK less scenario, I'm thinking if a packet sniffer like Wireshark can capture a pause frame, then it means NIC is sending pause frames to higher layers I believe. Likewise in the DPDK scenario I should be able to see the pause frames maybe in the PMD driver? Thanks, Alireza