All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco <ctxspi@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: XDP Redirect detail
Date: Sun, 24 Apr 2022 09:30:30 +0200	[thread overview]
Message-ID: <CAAVAo4M8HdA4yGpoVNo=-dAjXJ9tze77q5Rqvxu0TZ=VK2gNoQ@mail.gmail.com> (raw)
In-Reply-To: <87lew53qrs.fsf@toke.dk>

Hi Toke

Your information is very useful for me.

Thanks for your reply.

Marco

Il giorno sab 16 apr 2022 alle ore 19:02 Toke Høiland-Jørgensen
<toke@redhat.com> ha scritto:
>
> Marco <ctxspi@gmail.com> writes:
>
> > Hi
> >
> > Can XDP_REDIRECT forward packets to egress interface with speed
> > different than ingress interface?
> >
> > More precisely, if ingress interface speed is 100 Gbps and the egress
> > interface speed is 10 Gbps, the xdp program can be load on two
> > interfaces and forward traffic (using XDP_REDIRECT) between them?
>
> Well, yes, it can forward packets just fine; but it'll just forward each
> packet as it comes in, there's no mechanism for queueing or otherwise
> rate limiting them. 10->100G is fine, of course, but in the other
> direction, if you are receiving at 100Gbps line rate, you'll end up
> forwarding 10 Gbps of it out the 10G interface and dropping the rest,
> semi-randomly as the TX buffers overflow.
>
> We're working on adding a  queueing mechanism to XDP to help with this,
> but it'll probably be a little while yet before it surfaces...
>
> -Toke
>


-- 
E' meglio coltivare GNU/Linux... tanto Windows si pianta da solo!!

  reply	other threads:[~2022-04-24  7:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16  9:43 XDP Redirect detail Marco
2022-04-16 17:02 ` Toke Høiland-Jørgensen
2022-04-24  7:30   ` Marco [this message]
     [not found]   ` <CAAVAo4OaTBRHy1bhw4YGSG07-BfP6u6ybfO+cS6hr2xYiwvJCw@mail.gmail.com>
2022-04-25  7:29     ` Toke Høiland-Jørgensen

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='CAAVAo4M8HdA4yGpoVNo=-dAjXJ9tze77q5Rqvxu0TZ=VK2gNoQ@mail.gmail.com' \
    --to=ctxspi@gmail.com \
    --cc=toke@redhat.com \
    --cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.