2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
# Makefile for the linux networking.
|
|
|
|
#
|
|
|
|
# 2 Sep 2000, Christoph Hellwig <hch@infradead.org>
|
|
|
|
# Rewritten to use lists instead of if-statements.
|
|
|
|
#
|
|
|
|
|
|
|
|
obj-y := nonet.o
|
|
|
|
|
|
|
|
obj-$(CONFIG_NET) := socket.o core/
|
|
|
|
|
|
|
|
tmp-$(CONFIG_COMPAT) := compat.o
|
|
|
|
obj-$(CONFIG_NET) += $(tmp-y)
|
|
|
|
|
|
|
|
# LLC has to be linked before the files in net/802/
|
|
|
|
obj-$(CONFIG_LLC) += llc/
|
|
|
|
obj-$(CONFIG_NET) += ethernet/ 802/ sched/ netlink/
|
2005-08-09 20:30:24 -06:00
|
|
|
obj-$(CONFIG_NETFILTER) += netfilter/
|
2005-11-14 16:25:59 -07:00
|
|
|
obj-$(CONFIG_INET) += ipv4/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_XFRM) += xfrm/
|
|
|
|
obj-$(CONFIG_UNIX) += unix/
|
2011-03-03 16:35:07 -07:00
|
|
|
obj-$(CONFIG_NET) += ipv6/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_PACKET) += packet/
|
|
|
|
obj-$(CONFIG_NET_KEY) += key/
|
|
|
|
obj-$(CONFIG_BRIDGE) += bridge/
|
net: Distributed Switch Architecture protocol support
Distributed Switch Architecture is a protocol for managing hardware
switch chips. It consists of a set of MII management registers and
commands to configure the switch, and an ethernet header format to
signal which of the ports of the switch a packet was received from
or is intended to be sent to.
The switches that this driver supports are typically embedded in
access points and routers, and a typical setup with a DSA switch
looks something like this:
+-----------+ +-----------+
| | RGMII | |
| +-------+ +------ 1000baseT MDI ("WAN")
| | | 6-port +------ 1000baseT MDI ("LAN1")
| CPU | | ethernet +------ 1000baseT MDI ("LAN2")
| |MIImgmt| switch +------ 1000baseT MDI ("LAN3")
| +-------+ w/5 PHYs +------ 1000baseT MDI ("LAN4")
| | | |
+-----------+ +-----------+
The switch driver presents each port on the switch as a separate
network interface to Linux, polls the switch to maintain software
link state of those ports, forwards MII management interface
accesses to those network interfaces (e.g. as done by ethtool) to
the switch, and exposes the switch's hardware statistics counters
via the appropriate Linux kernel interfaces.
This initial patch supports the MII management interface register
layout of the Marvell 88E6123, 88E6161 and 88E6165 switch chips, and
supports the "Ethertype DSA" packet tagging format.
(There is no officially registered ethertype for the Ethertype DSA
packet format, so we just grab a random one. The ethertype to use
is programmed into the switch, and the switch driver uses the value
of ETH_P_EDSA for this, so this define can be changed at any time in
the future if the one we chose is allocated to another protocol or
if Ethertype DSA gets its own officially registered ethertype, and
everything will continue to work.)
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Tested-by: Nicolas Pitre <nico@marvell.com>
Tested-by: Byron Bradley <byron.bbradley@gmail.com>
Tested-by: Tim Ellis <tim.ellis@mac.com>
Tested-by: Peter van Valderen <linux@ddcrew.com>
Tested-by: Dirk Teurlings <dirk@upexia.nl>
Signed-off-by: David S. Miller <davem@davemloft.net>
2008-10-07 07:44:02 -06:00
|
|
|
obj-$(CONFIG_NET_DSA) += dsa/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_IPX) += ipx/
|
|
|
|
obj-$(CONFIG_ATALK) += appletalk/
|
|
|
|
obj-$(CONFIG_X25) += x25/
|
|
|
|
obj-$(CONFIG_LAPB) += lapb/
|
|
|
|
obj-$(CONFIG_NETROM) += netrom/
|
|
|
|
obj-$(CONFIG_ROSE) += rose/
|
|
|
|
obj-$(CONFIG_AX25) += ax25/
|
2007-11-16 16:52:17 -07:00
|
|
|
obj-$(CONFIG_CAN) += can/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_IRDA) += irda/
|
|
|
|
obj-$(CONFIG_BT) += bluetooth/
|
|
|
|
obj-$(CONFIG_SUNRPC) += sunrpc/
|
2007-04-26 16:48:28 -06:00
|
|
|
obj-$(CONFIG_AF_RXRPC) += rxrpc/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_ATM) += atm/
|
2010-04-02 00:18:33 -06:00
|
|
|
obj-$(CONFIG_L2TP) += l2tp/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_DECNET) += decnet/
|
2008-09-22 21:03:00 -06:00
|
|
|
obj-$(CONFIG_PHONET) += phonet/
|
2008-07-08 04:23:36 -06:00
|
|
|
ifneq ($(CONFIG_VLAN_8021Q),)
|
|
|
|
obj-y += 8021q/
|
|
|
|
endif
|
2005-08-09 21:14:34 -06:00
|
|
|
obj-$(CONFIG_IP_DCCP) += dccp/
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_IP_SCTP) += sctp/
|
2009-02-24 08:30:39 -07:00
|
|
|
obj-$(CONFIG_RDS) += rds/
|
2010-06-26 18:00:25 -06:00
|
|
|
obj-$(CONFIG_WIRELESS) += wireless/
|
2007-05-05 12:45:53 -06:00
|
|
|
obj-$(CONFIG_MAC80211) += mac80211/
|
2006-01-02 11:04:38 -07:00
|
|
|
obj-$(CONFIG_TIPC) += tipc/
|
2006-08-03 17:48:37 -06:00
|
|
|
obj-$(CONFIG_NETLABEL) += netlabel/
|
2007-02-08 14:37:42 -07:00
|
|
|
obj-$(CONFIG_IUCV) += iucv/
|
2007-05-07 01:34:20 -06:00
|
|
|
obj-$(CONFIG_RFKILL) += rfkill/
|
2007-07-10 16:57:28 -06:00
|
|
|
obj-$(CONFIG_NET_9P) += 9p/
|
2010-03-30 07:56:28 -06:00
|
|
|
obj-$(CONFIG_CAIF) += caif/
|
2008-11-25 02:02:08 -07:00
|
|
|
ifneq ($(CONFIG_DCB),)
|
|
|
|
obj-y += dcb/
|
2008-11-20 21:52:10 -07:00
|
|
|
endif
|
2010-06-26 18:00:25 -06:00
|
|
|
obj-$(CONFIG_IEEE802154) += ieee802154/
|
2012-05-15 14:50:20 -06:00
|
|
|
obj-$(CONFIG_MAC802154) += mac802154/
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
ifeq ($(CONFIG_NET),y)
|
|
|
|
obj-$(CONFIG_SYSCTL) += sysctl_net.o
|
|
|
|
endif
|
2008-12-23 17:18:24 -07:00
|
|
|
obj-$(CONFIG_WIMAX) += wimax/
|
2010-08-04 08:16:33 -06:00
|
|
|
obj-$(CONFIG_DNS_RESOLVER) += dns_resolver/
|
2010-04-06 16:14:15 -06:00
|
|
|
obj-$(CONFIG_CEPH_LIB) += ceph/
|
2010-12-13 04:19:28 -07:00
|
|
|
obj-$(CONFIG_BATMAN_ADV) += batman-adv/
|
2011-07-01 16:31:33 -06:00
|
|
|
obj-$(CONFIG_NFC) += nfc/
|
2011-10-25 20:26:31 -06:00
|
|
|
obj-$(CONFIG_OPENVSWITCH) += openvswitch/
|
VSOCK: Introduce VM Sockets
VM Sockets allows communication between virtual machines and the hypervisor.
User level applications both in a virtual machine and on the host can use the
VM Sockets API, which facilitates fast and efficient communication between
guest virtual machines and their host. A socket address family, designed to be
compatible with UDP and TCP at the interface level, is provided.
Today, VM Sockets is used by various VMware Tools components inside the guest
for zero-config, network-less access to VMware host services. In addition to
this, VMware's users are using VM Sockets for various applications, where
network access of the virtual machine is restricted or non-existent. Examples
of this are VMs communicating with device proxies for proprietary hardware
running as host applications and automated testing of applications running
within virtual machines.
The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
socket interface. The VM Sockets module supports both connection-oriented
stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
Sockets protocol family is defined as "AF_VSOCK" and the socket operations
split for SOCK_DGRAM and SOCK_STREAM.
For additional information about the use of VM Sockets, please refer to the
VM Sockets Programming Guide available at:
https://www.vmware.com/support/developer/vmci-sdk/
Signed-off-by: George Zhang <georgezhang@vmware.com>
Signed-off-by: Dmitry Torokhov <dtor@vmware.com>
Signed-off-by: Andy king <acking@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2013-02-06 07:23:56 -07:00
|
|
|
obj-$(CONFIG_VSOCKETS) += vmw_vsock/
|
2013-05-23 15:02:52 -06:00
|
|
|
obj-$(CONFIG_NET_MPLS_GSO) += mpls/
|
2013-10-30 14:10:47 -06:00
|
|
|
obj-$(CONFIG_HSR) += hsr/
|