search for: tcp_mem

...wing warning: The TCP receive window advertised by NFS client XXXXXXX is 5888. This is less than the recommended value of 32768 bytes. You should increase the TCP receive buffer size for NFS on the client. Some googling around got me to check these values for TCP: # sysctl net.ipv4.tcp_mem net.ipv4.tcp_mem = 98304 131072 196608 # sysctl net.ipv4.tcp_rmem net.ipv4.tcp_rmem = 4096 87380 4194304 # sysctl net.ipv4.tcp_wmem net.ipv4.tcp_wmem = 4096 16384 4194304 So these seem fine to me (i.e., the max is greater than 32768). Is there an NFS (as...

...net.ipv4.tcp_fin_timeout=30 net.ipv4.tcp_keepalive_intvl=10 net.ipv4.tcp_keepalive_probes=7 net.ipv4.tcp_keepalive_time=1800 net.ipv4.tcp_max_tw_buckets=360000 net.ipv4.tcp_synack_retries=3 net.ipv4.tcp_rmem="4096 87380 16777216" net.ipv4.tcp_wmem="4096 87380 16777216" net.ipv4.tcp_mem="8388608 8388608 8388608" ---------errors----------- # sysctl -p [errors] error: unknown error 22 setting key 'net.ipv4.tcp_rmem' error: unknown error 22 setting key 'net.ipv4.tcp_wmem' error: unknown error 22 setting key 'net.ipv4.tcp_mem' any advice?

Hi list (and happy new year), I'm experiencing some troubles using Samba (4.1.17 debian version) over VPN. Basically we've following setup : PC === LAN ===> VPN (WAN) ==== LAN ===> Samba file Server Copying big (say > 1MiB) files from PC to Samba file server almost always ends up with a NT_STATUS_IO_TIMEOUT error (or "a network error occured" if trying to copy from

...efault = 262144 # Controls IP default send buffer size (bytes) net.core.wmem_default = 262144 # Controls IP maximum receive buffer size (bytes) net.core.rmem_max = 262144 # Controls IP maximum send buffer size (bytes) net.core.wmem_max = 262144 # Controls TCP memory utilization (pages) net.ipv4.tcp_mem = 49152 65536 98304 # Controls TCP sliding receive window buffer (bytes) net.ipv4.tcp_rmem = 4096 87380 16777216 # Controls TCP sliding send window buffer (bytes) net.ipv4.tcp_wmem = 4096 65536 16777216 Ross S. W. Walker Information Systems Manager Medallion Financial, Corp. 437 Madison Avenue...

...ed stuff for Gig. sysctl -w net.core.rmem_max=8388608 sysctl -w net.core.wmem_max=8388608 sysctl -w net.core.rmem_default=65536 sysctl -w net.core.wmem_default=65536 sysctl -w net.ipv4.tcp_rmem='4096 87380 8388608' sysctl -w net.ipv4.tcp_wmem='4096 65536 8388608' sysctl -w net.ipv4.tcp_mem='8388608 8388608 8388608' sysctl -w net.ipv4.route.flush=1 Brian M. Duncan Katten Muchin Rosenman LLP 525 West Monroe Street Chicago IL 60661-3693 312-577-8045 brian.duncan@kattenlaw.com =========================================================== Important: This electronic mail me...

...lro off; -G ${DEVICE} rx 128 tx 128" ______________________________________________ sysctl.conf: net.core.rmem_max = 65536 net.core.wmem_max = 65536 net.core.rmem_default = 32768 net.core.wmem_default = 32768 net.ipv4.tcp_rmem = 4096 32768 65536 net.ipv4.tcp_wmem = 4096 32768 65536 net.ipv4.tcp_mem = 4096 32768 65536 net.ipv4.udp_mem = 4096 32768 65536 net.ipv4.tcp_moderate_rcvbuf = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_dsack = 1 ______________________________________________ smb.conf: socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE max xmit = 32768 -------------- next part ------...

..._________________________________________ > > sysctl.conf: > > net.core.rmem_max = 65536 > net.core.wmem_max = 65536 > net.core.rmem_default = 32768 > net.core.wmem_default = 32768 > net.ipv4.tcp_rmem = 4096 32768 65536 > net.ipv4.tcp_wmem = 4096 32768 65536 > net.ipv4.tcp_mem = 4096 32768 65536 > net.ipv4.udp_mem = 4096 32768 65536 > net.ipv4.tcp_moderate_rcvbuf = 1 > net.ipv4.tcp_sack = 1 > net.ipv4.tcp_dsack = 1 > ______________________________________________ > > smb.conf: > > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE > ma...

OS: CentOS 5.0 x86. Hi, I am using CentOS 5.0 at home, ADSL ~16 Mbps/~1 Mbps Internet connection and my ping time to my ISP is 160-170 msec. When downloading something with Firefox, I am getting download speeds of about 100-180 KB/sec (for example when downloading SP2 of XP from MS server). Are the CentOS networking settings OK for this kind of latency, or do I have to change some settings?

...in/sysctl -w net.ipv4.tcp_keepalive_time=1800 /sbin/sysctl -w net.ipv4.tcp_max_tw_buckets=360000 /sbin/sysctl -w net.ipv4.tcp_synack_retries=3 /sbin/sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216" /sbin/sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216" /sbin/sysctl -w net.ipv4.tcp_mem="8388608 8388608 8388608" --------------snip--------------- p.s. these are meant for a specific technology we use, so not sure if everyone reading would be best served by using them, mileage may vary! : / -karlski

i all I use linux as GiGE router and have 6 NIC on it Those days the NIC interrupt takes around 100% CPU but the system is 4G memroy and 8 CPU. I can't see any error packet in this NIC interface too After I block the udp, the %CPU drops. but the UDP only takes around 8M in general We use UDP traffic for voice. Do you have any suggestion ? increase the kernel parameter? Thank you so much

...ax echo 163840 > /proc/sys/net/core/rmem_default echo 163840 > /proc/sys/net/core/wmem_default echo "4096 163840 262144" > /proc/sys/net/ipv4/tcp_rmem echo "4096 163840 262144" > /proc/sys/net/ipv4/tcp_wmem echo "49152 163840 262144" > /proc/sys/net/ipv4/tcp_mem These, however, have only helped each of the transfer types performance-wise (FTP especially, smbfs wasn't really affected at all). Does anybody have any idea why I'm seeing such a huge difference between the smbfs and smbclient numbers? Am I missing something obvious?

Hi, I''m doing some test on a network 10 gb nics and xen with version 3.1 i''m measuring 2.5 gb/sec from domU to an external physical machine with iperf. switching to 3.2 has reduced the measured performance to 40-50 Mb/sec. did anything change in the network interface? can someone help me? thanks _______________________________________________ Xen-users mailing list

...ax=8388608 sysctl -w net.core.wmem_max=8388608 sysctl -w net.core.rmem_default=65536 sysctl -w net.core.wmem_default=65536 sysctl -w net.ipv4.tcp_rmem=''4096 87380 8388608'' sysctl -w net.ipv4.tcp_wmem=''4096 65536 8388608'' sysctl -w net.ipv4.tcp_mem=''8388608 8388608 8388608'' sysctl -w net.ipv4.route.flush=1 TCOP="add" IPTOP="-A" #iptables -t mangle -N MYSHAPER-OUT ##iptables -t mangle -I POSTROUTING -d $LIMITNETSPEC -j MYSHAPER-OUT #iptables -t mangle -I POSTROUTING -o $WAN -j MYSH...

Hi all, I have a rhel 5.1 xen server with two rhel 3 ES hvm guests installed. Both rhel3 guests use an internal xen bridge (xenbr1) which it isn''t binded to any physical interface host. On this bridge throughput it is very very poor, only 2.5 Mbs. How can I increase this throughput??? Many thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

Hi, machine: AMD K6 200 MHz Linux distribution: Mandrake 8.1 kernel: compiled 2.4.21 applied this: #define PSCHED_CLOCK_SOURCE PSCHED_CPU in file linux/include/net/pkt_sched.h bevore compiled the kernel (described on http://www.docum.org/stef.coene/qos/faq/cache/40.html) bandwitch on eth0: 128kbit The most simple configuration - 122kbit guaranted for WWW (sport 80) and

Hi, I have a problem with file transfers between a windows systems and unix systems. I have one win32 desktop (intel e6400 2Gb Ram), one win32 laptop (p-m 2Ghz). Also one linux laptop (p-m 1.4GHz) and one opensolaris desktop (intel e4400 1GB Ram). The two laptops have built-in 100Mbit ethernet and desktops have 1Gbit ethernet on the motherboard. Both desktops use a Marvell Yukon. The file

...ogging %u user, %S share, %M machine" oplocks = no level2 oplocks = no nt acl support = no csc policy = disable set directory = no wide links = no follow symlinks = no We've tried tuning tcp part with the next things: echo 400000 400000 400000 > /proc/sys/net/ipv4/tcp_mem echo 400000 400000 400000 > /proc/sys/net/ipv4/tcp_rmem echo 400000 400000 400000 > /proc/sys/net/ipv4/tcp_wmem echo 1 > /proc/sys/net/ipv4/tcp_tw_recycle echo 0 > /proc/sys/net/ipv4/tcp_sack echo 8192 > /proc/sys/net/ipv4/tcp_max...

I have a beefy machine (Intel dual-quad core, 16GB memory 2 x GigE) I have loaded RHEL5.1-xen on the hardware and have created two logical systems: 4 cpus, 7.5 GB memory 1 x Gige Following RHEL guidelines, I have it set up so that eth0->xenbr0 and eth1->xenbr1 Each of the two RHEL5.1 guests uses one of the interfaces and this is verified at the switch by seeing the unique MAC addresses.

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-03 16:49 ------- We haven't seen this