All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Eykholt <jre@nuovasystems.com>
To: jgarzik@pobox.com, fubar@us.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] bonding: allow L2 receive on slaves
Date: Wed, 07 May 2008 23:12:52 -0700	[thread overview]
Message-ID: <482299E4.80802@nuovasystems.com> (raw)

Hi Jay and Jeff,

I'm new on this alias and the patch set I submitted on 5/4 is my first 
for Linux.

I'm not sure I'm doing this right, but I have seen no comments at all 
about the
changes.  Would you make some suggestions as to how I should proceed? 

I'm willing to rewrite the patch as necessary to get the problem solved. 
If there's an issue on the basic idea, please let me know what it is.

I saw another recent patch that would allow LLDP to be delivered
on the bond even if it arrived on an inactive slave.  If it would
be more acceptable, we could add FCoE and FIP (being discussed in T11)
as two other exceptions.  This would be low impact as well, but not
as nice for the protocols, IMHO.   For example, if an L2 protocol had
a packet_type using a slave before the bond was created, it would
be cut off from any traffic.

Again, any suggestions would be appreciated. 
I know everyone is busy, so thanks for your time.

    Cheers,
    Joe Eykholt

             reply	other threads:[~2008-05-08  6:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  6:12 Joe Eykholt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-05  3:00 [PATCH 0/3] bonding: allow L2 receive on slaves Joe Eykholt

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=482299E4.80802@nuovasystems.com \
    --to=jre@nuovasystems.com \
    --cc=fubar@us.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@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.