DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: qcqx-obaq.6cba8489@hashmail.org
Cc: dev@dpdk.org
Subject: Re: dpdk-devbind.py ./. bonding interfaces
Date: Tue, 28 Jun 2022 19:09:21 -0700	[thread overview]
Message-ID: <20220628190921.591c6c85@hermes.local> (raw)
In-Reply-To: <YrZE/aZN09zSDMCr@priv-mua>

On Sat, 25 Jun 2022 01:13:01 +0200
qcqx-obaq.6cba8489@hashmail.org wrote:

> To whom it may concern.
> 
> usertools/dpdk-devbind.py currently does not recognize interfaces 
> that are part of a bond as active.
> that can be a nuisance if you are using something like libmoon which
> proactively rebinds drivers for all "not active" interfaces.
> 
> yes, i am aware of the dpdk contribution guideline. 
> 
> no, i am not going to jump through linux-kernel level hoops for
> a trivial 9-sloc-python driveby-contrib.
> 
> yes, that glorious code is all written by me, i promise i didnt
> steal it, and whoever takes pity and merges it is free to claim
> full credits for it.
> (if you feel bad about claiming credits for something you didnt
>  write, perhaps find more useful names for "f" and "l" and/or
>  add some comment above it...)
> 
> yes, i promise i will read and respect the contrib guide if i ever
> want to contrib code that took longer to write than it takes to
> read the contrib guide.
> 
> regards,
>    x23

Sounds like a libmoon bug, not a DPDK bug. 

There are many more types of joined devices in Linux, and just doing
bonding seems wrong.

Also, since your patch is missing Signed-off-by with a valid name,
it can not be accepted.

      reply	other threads:[~2022-06-29  2:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 23:13 qcqx-obaq.6cba8489
2022-06-29  2:09 ` Stephen Hemminger [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=20220628190921.591c6c85@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=qcqx-obaq.6cba8489@hashmail.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).