From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 78C5243175 for <public@inbox.dpdk.org>; Mon, 16 Oct 2023 01:13:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC3D740299; Mon, 16 Oct 2023 01:13:49 +0200 (CEST) Received: from mail-pf1-f173.google.com (mail-pf1-f173.google.com [209.85.210.173]) by mails.dpdk.org (Postfix) with ESMTP id A97B640269 for <users@dpdk.org>; Mon, 16 Oct 2023 01:13:48 +0200 (CEST) Received: by mail-pf1-f173.google.com with SMTP id d2e1a72fcca58-6be0277c05bso249312b3a.0 for <users@dpdk.org>; Sun, 15 Oct 2023 16:13:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1697411627; x=1698016427; 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=57v3PnrXoeA32G9kryCA8r9FIw5knl9C1UKtxYmCT+s=; b=NO43xAOLmcA6LkFW6B/tN42Lm/SIwDBAFTvWLvSwx+oMRD0JeSk0nKVkbES9FGZdi4 ZfC5u6Ya77pmNDnZCs8ISE74SLgp68SOHXl7T+b/5ZwsmNKVCqKRADp7kZBLXrvYy3x0 QbCQ0LmUdrd9+PjN731omm2PFmVUnhb7FEeLLvpIPhmO4NZ8nA+RGP9veB+St2hh1DYH e7YcWLLSvdmifFYdzEEAsG2YqwXVo2z927VG5tmllXmTHYa5y+H2KhFaBZr/a4E2a75Y dlXcRme20a6w2292ikiRJk+H0zwdWE3vA7Dq/C3OGHdItiG0Hdt0ZUNbRr5xJSyyp5w4 nBIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697411627; x=1698016427; 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=57v3PnrXoeA32G9kryCA8r9FIw5knl9C1UKtxYmCT+s=; b=aj/+5pcVvN20tssLdxAXQO920AhQQ4x+kJuCi9nqzGNxCJ3H+wjtjH20Zz9WW9vXGq +l3WZicrP0yGjdN98zLeHg473bk+K1fK6FyXU6cKJyKIhjIMpU/T0PfVmilDwQZ7eFnO r6AcN9Bm1B4bxzwLy8+NfnJ/X6uk5l79TF3BoAK5lMiE6CvPonYMzGZQ67sARl+JlvCK GjQ+Ba1gq24AfT6Ox2cYGPpfmdyD6KvZBENQ66Zgaem68kN3IQ2RaRO2EUGl2AROGLZ/ nfQj4zHfIuKnWQg9fLarlbvKTG4ygABIumaSuvpZJW3s1fa80kKcSUzNEnbPViB2zN9i tY5A== X-Gm-Message-State: AOJu0YxSCZmF3ZaR10v6gSPXDGt9Ohgb/ws8pZy8YNnXo827ICOe2wsR N1IQL0W+spu4kY08z9Kn7/P5jQ== X-Google-Smtp-Source: AGHT+IFWGYYjQJ0fCx8919FlSslc4ieIzRzpmGvbK6GVRgAiKlUlVhMP97gBB4d3Tg++iyRDSuG23Q== X-Received: by 2002:a05:6a00:16cd:b0:68b:a137:3739 with SMTP id l13-20020a056a0016cd00b0068ba1373739mr32732274pfc.4.1697411627476; Sun, 15 Oct 2023 16:13:47 -0700 (PDT) Received: from hermes.local (204-195-126-68.wavecable.com. [204.195.126.68]) by smtp.gmail.com with ESMTPSA id s6-20020aa78286000000b0065a1b05193asm16792900pfm.185.2023.10.15.16.13.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 15 Oct 2023 16:13:47 -0700 (PDT) Date: Sun, 15 Oct 2023 16:13:45 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Alireza Sadeghpour <alireza0101sadeghpour@gmail.com> Cc: users@dpdk.org Subject: Re: How to establish a uni-directional Ethernet link in the dpdk environment Message-ID: <20231015161345.45a9e487@hermes.local> In-Reply-To: <CAA=oK3PeeL6oz-eYmmxBDSZVCkfWFOSzHS+H9d9SvTnpDUO5yw@mail.gmail.com> References: <CAA=oK3PeeL6oz-eYmmxBDSZVCkfWFOSzHS+H9d9SvTnpDUO5yw@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org On Sun, 15 Oct 2023 10:30:48 +0330 Alireza Sadeghpour <alireza0101sadeghpour@gmail.com> wrote: > Hi, > > I am trying to establish a uni-directional Ethernet link where a singular > fiber is used to transmit data to the receiver in the DPDK environment. The > Rx of the transmit side and the Tx of the receive side are not physically > connected, like in a Data diode scenario. The ethernet controller on both > sides is intel 82580. > > my problem is that when I detach the RX line from one side, both sides' > links go down. > > Could anyone please give me some advice to solve this problem and establish > a valid unidirectional ethernet link? This is not a DPDK problem. Trying to non-standard configuration like this requires detailed knowledge of the hardware registers, and likely driver specific changes to do that. It is possible to bring up device in normal full duplex mode and even setup the receive queues but ignore them. But that doesn't sound like what you want.