From: Ben Hutchings <bhutchings@solarflare.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: <jhs@mojatatu.com>, <shemminger@vyatta.com>,
<kernel@wantstofly.org>, <hadi@cyberus.ca>, <roprabhu@cisco.com>,
<mst@redhat.com>, <netdev@vger.kernel.org>,
<gregory.v.rose@intel.com>, <davem@davemloft.net>
Subject: Re: [RFC PATCH 2/3] net: expose ebridge FDB with priv flag IFF_OFFLOADED_FDB
Date: Fri, 2 Mar 2012 20:00:42 +0000 [thread overview]
Message-ID: <1330718442.2611.37.camel@bwh-desktop> (raw)
In-Reply-To: <1330718193.2611.36.camel@bwh-desktop>
On Fri, 2012-03-02 at 19:56 +0000, Ben Hutchings wrote:
[...]
> General comment: why should the software bridge code be loaded in order
> to control a hardware bridge? (It's not even the only software bridge
> we have!) It would perhaps be neater to have separate modules for the
> software bridge, the rtnetlink bridge ops, and the glue functions for
> hardware bridges. But that could be done later.
I see from the other thread that you're already well aware for this.
So, no need to answer it.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-03-02 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 7:17 [RFC PATCH 0/3] net: bridge: propagate FDB table into hardware John Fastabend
2012-02-29 7:17 ` [RFC PATCH 1/3] net: refactor br_fdb_xxx rtnetlink routines John Fastabend
2012-02-29 7:17 ` [RFC PATCH 2/3] net: expose ebridge FDB with priv flag IFF_OFFLOADED_FDB John Fastabend
2012-03-02 19:56 ` Ben Hutchings
2012-03-02 20:00 ` Ben Hutchings [this message]
2012-03-06 3:34 ` John Fastabend
2012-02-29 7:17 ` [RFC PATCH 3/3] net: drivers: set IFF_OFFLOADED_FDB priv flag on ixgbe and igb John Fastabend
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=1330718442.2611.37.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=hadi@cyberus.ca \
--cc=jhs@mojatatu.com \
--cc=john.r.fastabend@intel.com \
--cc=kernel@wantstofly.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=roprabhu@cisco.com \
--cc=shemminger@vyatta.com \
/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).