DPDK usage discussions
 help / color / mirror / Atom feed
From: dave seddon <dave.seddon.ca@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Alireza Sadeghpour <alireza0101sadeghpour@gmail.com>, users@dpdk.org
Subject: Re: How to establish a uni-directional Ethernet link in the dpdk environment
Date: Sun, 15 Oct 2023 18:12:02 -0700	[thread overview]
Message-ID: <CANypexT10MPc2UrVcwUOEs29Qxud_4E_wbf07BnmXWHGOhVhEw@mail.gmail.com> (raw)
In-Reply-To: <20231015161345.45a9e487@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

Normally, if you're doing "single fiber optics" it basically means you have
a single color/frequency in one direction, and another color/frequency,
which is slightly offset.  e.g. They say blue for send, and purple for
recieve, or something like that.  It's hard to screw it up, but I've
definitely tried :)

On Sun, Oct 15, 2023 at 4:21 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> 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.
>


-- 
Regards,
Dave Seddon
+1 415 857 5102

[-- Attachment #2: Type: text/html, Size: 2191 bytes --]

      reply	other threads:[~2023-10-16  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15  7:00 Alireza Sadeghpour
2023-10-15 23:13 ` Stephen Hemminger
2023-10-16  1:12   ` dave seddon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANypexT10MPc2UrVcwUOEs29Qxud_4E_wbf07BnmXWHGOhVhEw@mail.gmail.com \
    --to=dave.seddon.ca@gmail.com \
    --cc=alireza0101sadeghpour@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).