Displaying 13 results from an estimated 13 matches for "__br_forward".
2006 Dec 08
2
Lots of "swapper: page allocation failure" and other memory related messages - 2.6.16-xen0
...nf_iterate+0x3f/0x6d
Dec 8 12:19:26 server kernel: [br_forward_finish+0/65] br_forward_finish+0x0/0x41
Dec 8 12:19:26 server kernel: [nf_hook_slow+71/193] nf_hook_slow+0x47/0xc1
Dec 8 12:19:26 server kernel: [br_forward_finish+0/65] br_forward_finish+0x0/0x41
Dec 8 12:19:26 server kernel: [__br_forward+70/87] __br_forward+0x46/0x57
Dec 8 12:19:26 server kernel: [br_forward_finish+0/65] br_forward_finish+0x0/0x41
Dec 8 12:19:26 server kernel: [br_flood+116/207] br_flood+0x74/0xcf
Dec 8 12:19:26 server kernel: [__br_forward+0/87] __br_forward+0x0/0x57
Dec 8 12:19:26 server kernel: [br_flood...
2018 Jan 10
1
soft lockup after set multicast_router of bridge and it's port to 2
...880be7e100028813 ffff882002b9ce80 ffff882002b9ce80 ffffffffa04f3930
<d> 00000000880be7e1 ffff882002b9ce80 ffff882002b9ce80 ffff88200286c042
<d> ffff88202ae7c6e0 ffff882002b9ceb8 ffff88013bc03950 ffffffffa04f36d5
Call Trace:
<IRQ>
[<ffffffffa04f3930>] ? __br_forward+0x0/0xd0 [bridge]
[<ffffffffa04f36d5>] ? br_multicast_forward+0x15/0x20 [bridge]
[<ffffffffa04f4a34>] ? br_handle_frame_finish+0x144/0x2a0 [bridge]
[<ffffffffa04fa938>] ? br_nf_pre_routing_finish+0x238/0x350 [bridge]
[<ffffffffa04faedb>] ? br_nf_pre_routi...
2006 Jan 26
0
Profiling hotspots in my tc filter ruleset
Hi,
after I saw that my machine was having problems to forward
more than 200 Mbit/s, I decided to profile the kernel and
find out the hotspots. This is what I found:
[...]
1028 bridge.ko __br_forward
1033 bridge.ko br_nf_forward_finish
1074 bridge.ko ip_sabotage_in
1119 ebtable_filter.ko ebt_hook
1177 sky2.ko sky2_phy_stats
1304 bridge.ko setup_pre_routing
1417 bridge.ko br_fdb_cleanup
14...
2009 Nov 08
9
2.6.31 xenified kernel - not ready for production
Hi,
I just want to know if somebody use 2.6.31.4 xenified kernel (aka
OpenSUSE) in production?
We have been testing it on new Nehalem Xeon server for few weeks w/o
any problem.
But as soon we tried it on production machine - after several
production domUs started - hard OS failure.
We had to switch back to 2.6.18.8 - xen stock kernel.
Peter
_______________________________________________
2007 Apr 18
2
[Bridge] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991!
..._end+45a6050/105dc880>
> >>ebp; cf00e000 <_end+ebe9820/105dc880>
> >>esp; c038fde0 <init_task_union+1de0/2000>
>
> Trace; c0284f25 <dev_queue_xmit+3b5/430>
> Trace; d0a112de <[bridge]__dev_queue_push_xmit+2e/60>
> Trace; d0a1132b <[bridge]__br_forward_finish+1b/60>
> Trace; d0a11503 <[bridge]br_flood+53/e0>
> Trace; d0a113d0 <[bridge]__br_forward+0/60>
> Trace; d0a115e7 <[bridge]br_flood_forward+27/30>
> Trace; d0a113d0 <[bridge]__br_forward+0/60>
> Trace; d0a12137 <[bridge]br_handle_frame_finish+107/...
2011 Dec 05
3
xen 4.0.1/w 2.6.32 swapper: page allocation failure
...2 01:29:39 xenhost-rack1 kernel: [4437064.012080]
[<ffffffff814b3067>] ? conntrack_mt_v2+0x1b/0x1d
Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.012121]
[<ffffffff81543be2>] ? br_forward_finish+0x0/0x53
Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.012124]
[<ffffffff81543c35>] ? __br_forward+0x0/0x9c
Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.012127]
[<ffffffff81543cbe>] __br_forward+0x89/0x9c
Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.012129]
[<ffffffff814792e6>] ? skb_clone+0x58/0x5d
Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.012132]
[<ffffffff81543b22>]...
2013 Apr 30
6
[Bridge] [PATCHv4 net-next 0/2] Add two new flags to bridge.
The following series adds 2 new flags to bridge. One flag allows
the user to control whether mac learning is performed on the interface
or not. By default mac learning is on.
The other flag allows the user to control whether unicast traffic
is flooded (send without an fdb) to a given unicast port. Default is
on.
Changes since v4:
- Implemented Stephen's suggestions.
Changes since v2:
-
2006 Jul 06
12
kernel BUG at net/core/dev.c:1133!
.../0x130
[<c05bbee0>] br_forward_finish+0x0/0x70
[<c04f0eab>] nf_iterate+0x6b/0xa0
[<c05bbee0>] br_forward_finish+0x0/0x70
[<c05bbee0>] br_forward_finish+0x0/0x70
[<c04f0f4e>] nf_hook_slow+0x6e/0x120
[<c05bbee0>] br_forward_finish+0x0/0x70
[<c05bc044>] __br_forward+0x74/0x80
[<c05bbee0>] br_forward_finish+0x0/0x70
[<c05bceb1>] br_handle_frame_finish+0xd1/0x160
[<c05bcde0>] br_handle_frame_finish+0x0/0x160
[<c05c0e0b>] br_nf_pre_routing_finish+0xfb/0x480
[<c05bcde0>] br_handle_frame_finish+0x0/0x160
[<c05c0d10>] br_nf_...
2009 Jun 15
1
[Bridge] [PATCH][RFC] net/bridge: add basic VEPA support
...length(const struct sk_buff *skb)
@@ -92,6 +93,17 @@ void br_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
}
/* called with rcu_read_lock */
+void br_vepa_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
+{
+ if (!skb_warn_if_lro(skb) && (to != NULL)) {
+ __br_forward(to, skb);
+ return;
+ }
+
+ kfree_skb(skb);
+}
+
+/* called with rcu_read_lock */
void br_forward(const struct net_bridge_port *to, struct sk_buff *skb)
{
if (should_deliver(to, skb)) {
@@ -109,11 +121,19 @@ static void br_flood(struct net_bridge *br, struct sk_buff *skb,
{
struct net_bridg...
2009 Jun 15
1
[Bridge] [PATCH][RFC] net/bridge: add basic VEPA support
...length(const struct sk_buff *skb)
@@ -92,6 +93,17 @@ void br_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
}
/* called with rcu_read_lock */
+void br_vepa_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
+{
+ if (!skb_warn_if_lro(skb) && (to != NULL)) {
+ __br_forward(to, skb);
+ return;
+ }
+
+ kfree_skb(skb);
+}
+
+/* called with rcu_read_lock */
void br_forward(const struct net_bridge_port *to, struct sk_buff *skb)
{
if (should_deliver(to, skb)) {
@@ -109,11 +121,19 @@ static void br_flood(struct net_bridge *br, struct sk_buff *skb,
{
struct net_bridg...
2009 Jun 15
1
[Bridge] [PATCH][RFC] net/bridge: add basic VEPA support
...length(const struct sk_buff *skb)
@@ -92,6 +93,17 @@ void br_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
}
/* called with rcu_read_lock */
+void br_vepa_deliver(const struct net_bridge_port *to, struct sk_buff *skb)
+{
+ if (!skb_warn_if_lro(skb) && (to != NULL)) {
+ __br_forward(to, skb);
+ return;
+ }
+
+ kfree_skb(skb);
+}
+
+/* called with rcu_read_lock */
void br_forward(const struct net_bridge_port *to, struct sk_buff *skb)
{
if (should_deliver(to, skb)) {
@@ -109,11 +121,19 @@ static void br_flood(struct net_bridge *br, struct sk_buff *skb,
{
struct net_bridg...
2013 Feb 13
14
[Bridge] [PATCH v10 net-next 00/12] VLAN filtering/VLAN aware bridge
Changes since v9:
* series re-ordering so make functionality more distinct. Basic vlan
filtering is patches 1-4. Support for PVID/untagged vlans is patches
5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is
still additional egress policy.
* Slight simplification to code that extracts the VID from skb. Since we
now depend on the vlan module, at the time of input skb_tci is
2013 Jan 09
16
[Bridge] [PATCH net-next V5 00/14] Add basic VLAN support to bridges
This series of patches provides an ability to add VLANs to the bridge
ports. This is similar to what can be found in most switches. The bridge
port may have any number of VLANs added to it including vlan 0 priority tagged
traffic. When vlans are added to the port, only traffic tagged with particular
vlan will forwarded over this port. Additionally, vlan ids are added to FDB
entries and become