networking

tipc

TIPC


Introduction

TIPC is a LAN protocol, originally designed by Jon Maloy at Ericsson. Its purpose is to provide an efficient, transparent, and scalable communication mechanism for a wide range of possible cluster configurations. It has been in the linux kernel since 2.6.16.
http://tipc.sf.net is the main TIPC site.

talk:tcp_memory_documentation

stack:

call tree:
[] tcp_retransmit_skb+0x176/0x2dd

[] tcp_retransmit_timer

[] tcp_write_timer

[] tcp_write_timer

[] tcp_write

[] run_timer_softirq

[] __do_softirq


=

 smp_apic_timer_interrupt
 apic_timer_interrupt
 mwait_idle
 cpu_idle
 start_kernel

(o) kernel panic - not syncing: Fatal exception in interrupt

kevent

linuxnet:about

This Wiki is for documentation and discussions of development of the Linux Networking.

tipc_faq

networkmanager

NetworkManager is designed to be fully automatic and "Just Work" without intervention, but friendly desktop applications allow users to control the state of the network if they desire. NetworkManager keeps a list of all available network devices, and updates that list when you insert or remove new network cards, dock your laptop, etc. Using this list, NetworkManager determines the best device to use for the computer's network connection.

i/oat

bonding

The Linux bonding driver provides a method for aggregating
multiple network interfaces into a single logical
bonded interface.
The behavior of the bonded interfaces depends upon the mode; generally
speaking, modes provide either hot standby or load balancing services.
Additionally, link integrity monitoring may be performed.

sk_buff

All network-related queues and buffers in the kernel use a common data structure, struct sk_buff. This is a large struct containing all the control information required for the packet (datagram, cell, whatever). The sk_buff elements are organized as a doubly linked list, in such a way that it is very efficient to move an sk_buff element from the beginning/end of a list to the beginning/end of another list.

ifb

The Intermediate Functional Block device is the successor to the IMQ iptables module that was never integrated.
Advantage over current IMQ; cleaner in particular in SMP;
with a _lot_ less code. Old Dummy device functionality is preserved while new one only
kicks in if you use actions.

Syndicate content