Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:traffic (Results 1 - 25 of 314) sorted by null

1 2 3 4 5 6 7 8 91011>>

/external/srec/doc/logs/srec/
recog4_SHIP_liveaudio.res	11 R: traffic info 13 R: traffic
recog4_SHIP_bothtags5.res	33 R: traffic 39 R: traffic information 41 R: traffic memory
recog4_SHIP_bothtags5_from_saved.res	33 R: traffic 39 R: traffic information 41 R: traffic memory
/frameworks/base/core/java/android/ddm/
README.txt	1 Some classes that handle DDM traffic.
/external/iproute2/include/linux/
ip6_tunnel.h	11 /* copy the traffic class field from the inner packet */ 26 __be32 flowinfo; /* traffic class and flowlabel for tunnel */
/prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/
ip6_tunnel.h	13 /* copy the traffic class field from the inner packet */ 28 __be32 flowinfo; /* traffic class and flowlabel for tunnel */
/external/netcat/data/
pm.d	4 # used as a firewall, that starts routing IP traffic BEFORE its filter sets
/external/iproute2/man/man8/
tc-pfifo_fast.8	26 have traffic, higher bands are never dequeued. This can be used to 27 prioritize interactive traffic or penalize 'lowest cost' traffic.
tc.8	3 tc \- show / manipulate traffic control settings 61 is used to configure Traffic Control in the Linux kernel. Traffic Control consists 66 When traffic is shaped, its rate of transmission is under control. Shaping may 68 bursts in traffic for better network behaviour. Shaping occurs on egress. 73 for traffic that needs it while still guaranteeing bandwidth to bulk transfers. Reordering 78 Where shaping deals with transmission of traffic, policing pertains to traffic 83 Traffic exceeding a set bandwidth may also be dropped forthwith, both on 87 Processing of traffic is controlled by three kinds of objects: qdiscs,     [all...]
tc-tbf.8	25 traffic control with the 29 TBF is a pure shaper and never schedules traffic. It is non-work-conserving and may throttle 32 it is able to shape up to 1mbit/s of normal traffic with ideal minimal burstiness, 44 As the name implies, traffic is filtered based on the expenditure of 50 On creation, the TBF is stocked with tokens which correspond to the amount of traffic that can be burst
/external/ipsec-tools/src/racoon/samples/
racoon.conf.sample-natt	12 # traffic. Don't forget to open these ports on your firewall! 16 # for "normal" IKE traffic. IANA allocated port 500. 22 # ESP traffic. 30 # traffic between the peers. Normally the UDP-Encap traffic 40 # policy in the kernel SPD. For example for traffic between
/external/srec/config/en.us/grammars/
bothtags5.grxml	100 traffic information 104 traffic info 108 traffic 112 traffic memory
homonym_test1.grxml	104 traffic information 108 traffic info 112 traffic 116 traffic memory
homonym_test2.grxml	108 traffic information 112 traffic info 116 traffic 120 traffic memory
homonym_test3.grxml	107 traffic information 111 traffic info 115 traffic 119 traffic memory
homonym_test4.grxml	109 traffic information 113 traffic info 117 traffic 121 traffic memory
/hardware/ti/wlan/wl1271/stad/src/Sta_Management/
PowerMgr.h	87 TI_HANDLE hTrafficMonitor; /**< Handle to the Traffic Monitor object */ 126 * Traffic Monitor event (TrafficAlertElement) for 127 * the pass to active event from the traffic monitor. 130 * Traffic Monitor event (TrafficAlertElement) for 132 * traffic monitor. 135 * Traffic Monitor event (TrafficAlertElement) for 139 * Traffic Monitor event (TrafficAlertElement) for
/system/wlan/ti/sta_dk_4_0_4_32/common/src/Management/PowerMgr/
PowerMgr.h	96 TI_HANDLE hTrafficMonitor; /**< Handle to the Traffic Monitor object */ 133 * Traffic Monitor event (TrafficAlertElement) for 134 * the pass to active event from the traffic monitor. 137 * Traffic Monitor event (TrafficAlertElement) for 139 * traffic monitor. 142 * Traffic Monitor event (TrafficAlertElement) for 146 * Traffic Monitor event (TrafficAlertElement) for
/system/wlan/ti/wilink_6_1/stad/src/Sta_Management/
PowerMgr.h	87 TI_HANDLE hTrafficMonitor; /**< Handle to the Traffic Monitor object */ 126 * Traffic Monitor event (TrafficAlertElement) for 127 * the pass to active event from the traffic monitor. 130 * Traffic Monitor event (TrafficAlertElement) for 132 * traffic monitor. 135 * Traffic Monitor event (TrafficAlertElement) for 139 * Traffic Monitor event (TrafficAlertElement) for
/hardware/ti/wlan/wl1271/stad/src/Data_link/
TrafficMonitor.h	53 /*The max number of Alert Element that the traffic monitor will be able to Manage.*/ 78 /* The traffic manger class structure */ 96 /*to use in our "traffic down" timer */ 97 TI_BOOL DownTimerEnabled; /* Indicates whether the "down traffic" timer is active or not */
/system/wlan/ti/wilink_6_1/stad/src/Data_link/
TrafficMonitor.h	53 /*The max number of Alert Element that the traffic monitor will be able to Manage.*/ 78 /* The traffic manger class structure */ 96 /*to use in our "traffic down" timer */ 97 TI_BOOL DownTimerEnabled; /* Indicates whether the "down traffic" timer is active or not */
/external/tcpdump/tests/
ospf-gmpls.new	5 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 8 12 Traffic Engineering Metric subTLV (5), length: 4, Metric 63 29 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 9 36 Traffic Engineering Metric subTLV (5), length: 4, Metric 63 53 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 3 60 Traffic Engineering Metric subTLV (5), length: 4, Metric 1
ospf-gmpls.out	5 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 8 12 Traffic Engineering Metric subTLV (5), length: 4, Metric 63 29 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 9 36 Traffic Engineering Metric subTLV (5), length: 4, Metric 63 53 Area Local Opaque LSA (10), Opaque-Type: Traffic Engineering LSA (1), Opaque-ID: 3 60 Traffic Engineering Metric subTLV (5), length: 4, Metric 1
/external/iproute2/examples/
README.cbq	61 # DEVICE: eth0 - device where we do control our traffic 80 # RULE=10.1.1.0/24:80 - all traffic for network 10.1.1.0 to port 80 83 # RULE=:25,10.2.2.128/25:5000 - all traffic from any address and port 25 to 86 # RULE=10.5.5.5:80, - shaper active only for traffic from port 80 of 94 # All shapers do work only for outgoing traffic! 102 # Let all traffic from backbone to client will be shaped at 28Kbit and 103 # traffic from client to backbone - at 128Kbit. We need two config files:
/external/srec/config/en.us/tcp/
bothtags5.tcp	96 recognize_nist m252/m252a22e.nwv 0 0 traffic 99 recognize_nist m252/m252a11e.nwv 0 0 traffic information 100 recognize_nist m252/m252a21e.nwv 0 0 traffic memory

Completed in 560 milliseconds

1 2 3 4 5 6 7 8 91011>>