netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Christophe Devriese <Christophe.Devriese@eurid.eu>,
	netdev@vger.kernel.org
Subject: Re: Help with bugfix for bond active-backup mode + vlans
Date: Mon, 24 Jul 2006 14:35:30 -0700	[thread overview]
Message-ID: <44C53D22.6040908@candelatech.com> (raw)
In-Reply-To: <200607242125.k6OLPPhg019864@death.nxdomain.ibm.com>

Jay Vosburgh wrote:
> Ben Greear <greearb@candelatech.com> wrote:
> 
> 
>>Jay Vosburgh wrote:
>>
>>
>>>	Another possibility would be to have __vlan_hwaccel_rx check the
>>>VLAN_DEV_INFO(skb->dev)->real_dev, and if that's a bonding device, apply
>>>the same logic found in skb_bond().  Or, if there's some way to ask the
>>>question "is dev a VLAN device?", then that same test could be put into
>>>skb_bond() and all of the packet suppression fru fru could stay there.
>>
>>There is a flag in if.h to denote VLAN devices:
> 
> 
> 	Thanks, I missed that.
> 
> 	Sadly, elegance remains elusive, since the by the time skb_bond
> is called, the slave device the packet arrived on isn't available
> (vlan->real_dev points to 'bond0' by this point), and that information
> is needed to decide whether to drop the packet or not.
> 
> 	The least grotty solution that comes to mind is to have
> __vlan_hwaccel_rx call some skb_bond_suppress_dups() function directly,
> and change skb_bond() to also call that function.

Can you use skb->input_dev?

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2006-07-24 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 16:37 Help with bugfix for bond active-backup mode + vlans Christophe Devriese
2006-07-24 17:49 ` Jay Vosburgh
2006-07-24 17:58   ` Ben Greear
2006-07-24 21:25     ` Jay Vosburgh
2006-07-24 21:35       ` Ben Greear [this message]
2006-07-25  1:40         ` Jay Vosburgh

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=44C53D22.6040908@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Christophe.Devriese@eurid.eu \
    --cc=fubar@us.ibm.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 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).