search for: netif_rx

...DGE which auto constructed in the module initiation ,and defined as a global variable "brg".And I add one eth card(eth0) to the br as a port .The main program is just below this page. But now I meet one question ,that is ,when I want passup a skb to the higher protocol layer use function netif_rx ,the higher layer not response ,the skb must have not passup yet .Why ?I'm puzzling about it for some days . Sorry my english is so poor:) Thanks ! //my own bridge struct struct Bridge{ rwlock_t lock; rwlock_t hash_lock; struct net_device dev; struct Bridge_fdb_entry *hash[BR_HASH...

Second version, all feedback so far addressed, thanks for the help and interest! The patch to iproute2 has not changed, so I'm not including it this time. Patch 4/4 (the netlink interface) is basically unchanged as well but included for completeness. The other changes have moved forward a bit, to the point where I find them a lot cleaner and am more confident in the code being ready for

Second version, all feedback so far addressed, thanks for the help and interest! The patch to iproute2 has not changed, so I'm not including it this time. Patch 4/4 (the netlink interface) is basically unchanged as well but included for completeness. The other changes have moved forward a bit, to the point where I find them a lot cleaner and am more confident in the code being ready for

Second version, all feedback so far addressed, thanks for the help and interest! The patch to iproute2 has not changed, so I'm not including it this time. Patch 4/4 (the netlink interface) is basically unchanged as well but included for completeness. The other changes have moved forward a bit, to the point where I find them a lot cleaner and am more confident in the code being ready for

Not many changes this time, just integrated a bug fix and all the coding style feedback from Eric Dumazet and Patrick McHardy. I'll keep the patch for network namespaces on the tx path out of this series for now, because the discussion is still ongoing and it addresses an unrelated issue. --- Version 2 description: The patch to iproute2 has not changed, so I'm not including it this

Not many changes this time, just integrated a bug fix and all the coding style feedback from Eric Dumazet and Patrick McHardy. I'll keep the patch for network namespaces on the tx path out of this series for now, because the discussion is still ongoing and it addresses an unrelated issue. --- Version 2 description: The patch to iproute2 has not changed, so I'm not including it this

Not many changes this time, just integrated a bug fix and all the coding style feedback from Eric Dumazet and Patrick McHardy. I'll keep the patch for network namespaces on the tx path out of this series for now, because the discussion is still ongoing and it addresses an unrelated issue. --- Version 2 description: The patch to iproute2 has not changed, so I'm not including it this

...2 2009 -0800 @@ -432,15 +432,11 @@ u16 tag = le16_to_cpu(rx_desc->wb.upper.vlan); #ifdef CONFIG_XEN_NETDEV2_BACKEND - if(ring->queue_index) { + if ((adapter->flags & IXGBE_FLAG_VMDQ_ENABLED) && ring->queue_index) { /* This is a VMDq packet destined for a VM. */ vmq_netif_rx(skb, ring->queue_index); return; } - else { - netif_rx(skb); - return; - } #endif #ifndef IXGBE_NO_INET_LRO if (adapter->netdev->features & NETIF_F_LRO && @@ -524,7 +520,8 @@ adapter->hw_csum_rx_good++; #ifdef CONFIG_XEN_NETDEV2_BACKEND - skb->proto_data_va...

...a <generic_make_request+10a/120> Trace; c013a636 <__refile_buffer+56/60> Trace; c01bedfd <submit_bh+4d/70> Trace; c01bef97 <ll_rw_block+177/1c0> Trace; c016e4fd <journal_brelse_array+1d/30> Trace; c016d65b <journal_commit_transaction+3ab/10f2> Trace; c02227c9 <netif_rx+a9/1d0> Trace; c021eb2f <alloc_skb+ef/1c0> Trace; c01c5cd7 <receive_packet+2c7/3e0> Trace; c0170236 <kjournald+136/200> Trace; c01700e0 <commit_timeout+0/10> Trace; c0105676 <kernel_thread+26/30> Trace; c0170100 <kjournald+0/200> Code; c0130956 <__free_pag...

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

This is based on an earlier patch from Eric Biederman adding forwarding between macvlans. I extended his approach to allow the administrator to choose the mode for each macvlan, and to implement a functional VEPA between macvlan. Still missing from this is support for communication between the lower device that the macvlans are based on. This would be extremely useful but as others have found out

...emcpy) = 0x236c8c64 kernel(memmove) = 0xa3a5be95 kernel(memset) = 0xde0bdcff kernel(module_layout) = 0x14522340 kernel(mutex_lock) = 0xfee8a795 kernel(mutex_unlock) = 0x03758301 kernel(net_assign_generic) = 0xa43636ec kernel(net_namespace_list) = 0x6d2fc5a6 kernel(net_ratelimit) = 0xf6ebc03b kernel(netif_rx) = 0x75484296 kernel(netlink_broadcast) = 0x00312919 kernel(netlink_set_err) = 0xb3a0e7bb kernel(netlink_unicast) = 0x27418d14 kernel(nf_conntrack_destroy) = 0xd83791bc kernel(nla_find) = 0x444779c4 kernel(nla_memcpy) = 0xf1db1704 kernel(nla_parse) = 0xa58b6804 kernel(nla_put) = 0x37587aff kernel(n...

...if (dev->features & NETIF_F_NO_CSUM) + skb->ip_summed = CHECKSUM_UNNECESSARY; + pr_debug("Receiving skb proto 0x%04x len %i type %i\n", + ntohs(skb->protocol), skb->len, skb->pkt_type); + + dev->stats.rx_bytes += skb->len; + dev->stats.rx_packets++; + netif_rx(skb); + } + return done ? IRQ_HANDLED : IRQ_NONE; +} + +static int lguestnet_open(struct net_device *dev) +{ + int i; + struct lguestnet_info *info = dev->priv; + + /* Set up our MAC address */ + memcpy(info->peer[info->me].mac, dev->dev_addr, ETH_ALEN); + + /* Turn on promisc mode if n...

...if (dev->features & NETIF_F_NO_CSUM) + skb->ip_summed = CHECKSUM_UNNECESSARY; + pr_debug("Receiving skb proto 0x%04x len %i type %i\n", + ntohs(skb->protocol), skb->len, skb->pkt_type); + + dev->stats.rx_bytes += skb->len; + dev->stats.rx_packets++; + netif_rx(skb); + } + return done ? IRQ_HANDLED : IRQ_NONE; +} + +static int lguestnet_open(struct net_device *dev) +{ + int i; + struct lguestnet_info *info = dev->priv; + + /* Set up our MAC address */ + memcpy(info->peer[info->me].mac, dev->dev_addr, ETH_ALEN); + + /* Turn on promisc mode if n...

Hello, guys, I am trying to get rshaper 2.01 to work on our Redhat 6.2 servers, but it does not seem to be able to control the bandwidth usage, here are the details, 1. Our production servers are all Redhat 6.2 with Kernel 2.2.19-6.2.12, the software we use are customized specifically for RH6.2, so I can''t upgrade to 2.4 kernel. 2. On my test server with the same RH6.2 and kernel (it has

vhost_net_ubuf_put_and_wait has a confusing name: it will actually also free it's argument. Thus since commit 1280c27f8e29acf4af2da914e80ec27c3dbd5c01 "vhost-net: flush outstanding DMAs on memory change" vhost_net_flush tries to use the argument after passing it to vhost_net_ubuf_put_and_wait, this results in use after free. To fix, don't free the argument in

vhost_net_ubuf_put_and_wait has a confusing name: it will actually also free it's argument. Thus since commit 1280c27f8e29acf4af2da914e80ec27c3dbd5c01 "vhost-net: flush outstanding DMAs on memory change" vhost_net_flush tries to use the argument after passing it to vhost_net_ubuf_put_and_wait, this results in use after free. To fix, don't free the argument in

Hello, I''m trying to setup Xen on a machine with 2 physical network devices using linux bonding without success. I haven''t received any answer on my question on xen-users, the only discussion on this seems to be at http://lists.xensource.com/archives/html/xen-devel/2005-10/msg01174.html Could someone shed some light on state/ plans regarding Xen and bonding? Regards --

This is the third version of the macvtap device driver, following another major restructuring and a lot of bug fixes: * Change macvtap to be based around a struct sock * macvtap: fix initialization * return 0 to netlink * don't use rcu for q->file and q->vlan pointers * macvtap: checkpatch.pl fixes * macvtap: fix tun IFF flags * Use a struct socket to make tx flow control work * disable