Network Perforamnce - It's just slow! Post: 303033114

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

network speed is slow

Hello, everyone: i encounter a problem these days , pls help me ,thanks in advance. my env: machine: ES40 A ES40 B os: true64 Unix 4.0f note: src.tar 8M network card speed 100M my problem: ...

2. AIX

How to send big files over slow network?

Hi, I am trying to send oracle archives over WAN and it is taking hell a lot of time. To reduce the time, I tried to gzip the files and send over to the other side. That seems to reduce the time. Does anybody have experienced this kind of problem and any possible ways to reduce the time. ...

3. Programming

Help in developing a Network Appliation to monitor pc in a network

I am developing a Network Appliation to monitor computers in a network. Specs are App monitors the current web page viewed in each system App also can shutdown the computer in the network App can show all process run by each computer in the network I am now confused how to start my...

4. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no...

5. Solaris

Unavailable/Slow Network Paths in $PATH

At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries. Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands...

6. Red Hat

slow network on RHEL5

hey guys, We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch. When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are...

7. UNIX for Advanced & Expert Users

Slow printing to network printers using CUPS

Hi Guys, I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower...

8. Solaris

Solaris 11.1 Slow Network Performance

I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are...

9. Red Hat

Network becomes slow and return fast only after restart network

Hi, I have 2 machines in production environment: 1. redhat machine for application 2. DB machine (oracle) The application doing a lot of small read&writes from and to the DB machine. The problem is that after some few hours the network from the application to the DB becomes very slow and...

LEARN ABOUT NETBSD

mskc

SK(4)							   BSD Kernel Interfaces Manual 						     SK(4)

NAME

     sk, skc -- SysKonnect XMAC II and Marvell GMAC based gigabit ethernet

SYNOPSIS

     skc* at pci? dev ? function ?
     sk* at skc?
     mskc* at pci? dev ? function ?
     msk* at skc?

DESCRIPTION

     The sk driver provides support for SysKonnect based gigabit ethernet adapters and Marvell based gigabit ethernet adapters, including the fol-
     lowing:

	   o   SK-9821 SK-NET GE-T single port, copper adapter
	   o   SK-9822 SK-NET GE-T dual port, copper adapter
	   o   SK-9841 SK-NET GE-LX single port, single mode fiber adapter
	   o   SK-9842 SK-NET GE-LX dual port, single mode fiber adapter
	   o   SK-9843 SK-NET GE-SX single port, multimode fiber adapter
	   o   SK-9844 SK-NET GE-SX dual port, multimode fiber adapter
	   o   SK-9521 V2.0 single port, copper adapter (32-bit)
	   o   SK-9821 V2.0 single port, copper adapter
	   o   SK-9843 V2.0 single port, copper adapter
	   o   3Com 3c940 single port, copper adapter
	   o   Belkin Gigabit Desktop Network PCI Card, single port, copper (32-bit)
	   o   D-Link DGE-530T single port, copper adapter
	   o   Linksys EG1032v2 single-port, copper adapter
	   o   Linksys EG1064v2 single-port, copper adapter

     The msk driver provides support for the Marvell Yukon-2 based Gigabit Ethernet adapters, including the following:

	   o   Marvell Yukon 88E8035, copper adapter
	   o   Marvell Yukon 88E8036, copper adapter
	   o   Marvell Yukon 88E8038, copper adapter
	   o   Marvell Yukon 88E8050, copper adapter
	   o   Marvell Yukon 88E8052, copper adapter
	   o   Marvell Yukon 88E8053, copper adapter
	   o   Marvell Yukon 88E8055, copper adapter
	   o   SK-9E21 1000Base-T single port, copper adapter
	   o   SK-9E22 1000Base-T dual port, copper adapter
	   o   SK-9E81 1000Base-SX single port, multimode fiber adapter
	   o   SK-9E82 1000Base-SX dual port, multimode fiber adapter
	   o   SK-9E91 1000Base-LX single port, single mode fiber adapter
	   o   SK-9E92 1000Base-LX dual port, single mode fiber adapter
	   o   SK-9S21 1000Base-T single port, copper adapter
	   o   SK-9S22 1000Base-T dual port, copper adapter
	   o   SK-9S81 1000Base-SX single port, multimode fiber adapter
	   o   SK-9S82 1000Base-SX dual port, multimode fiber adapter
	   o   SK-9S91 1000Base-LX single port, single mode fiber adapter
	   o   SK-9S92 1000Base-LX dual port, single mode fiber adapter
	   o   SK-9E21D 1000Base-T single port, copper adapter

     The SysKonnect based adapters consist of two main components: the XaQti Corp. XMAC II Gigabit MAC (sk) and the SysKonnect GEnesis controller
     ASIC (skc).  The XMAC provides the Gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet
     buffering and arbitration.  The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations.

     The Marvell based adapters are a single integrated circuit, but are still presented as a separate MAC (sk) and controller ASIC (skc).  At
     this time, there are no dual-port Marvell based NICs.

     The sk driver configures dual port SysKonnect adapters such that each XMAC is treated as a separate logical network interface.  Both ports
     can operate independently of each other and can be connected to separate networks.  The SysKonnect driver software currently only uses the
     second port on dual port adapters for failover purposes: if the link on the primary port fails, the SysKonnect driver will automatically
     switch traffic onto the second port.

     The XaQti XMAC II supports full and half duplex operation with autonegotiation.  The XMAC also supports unlimited frame sizes.  Support for
     jumbo frames is provided via the interface MTU setting.  Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the
     adapter to receive and transmit jumbo frames.  Using jumbo frames can greatly improve performance for certain tasks, such as file transfers
     and data streaming.

     Hardware TCP/IP checksum offloading for IPv4 is supported.

     The following media types and options (as given to ifconfig(8)) are supported:

	   media autoselect
		Enable autoselection of the media type and options.  The user can manually override the autoselected mode.

	   media 1000baseSX mediaopt full-duplex
		Set 1000Mbps (Gigabit Ethernet) operation on fiber and force full-duplex mode.

	   media 1000baseSX mediaopt half-duplex
		Set 1000Mbps (Gigabit Ethernet) operation on fiber and force half-duplex mode.

	   media 1000baseT mediaopt full-duplex
		Set 1000Mbps (Gigabit Ethernet) operation and force full-duplex mode.

     For more information on configuring this device, see ifconfig(8).	To view a list of media types and options supported by the card, try
     ifconfig -m <device>.  For example, ifconfig -m sk0.

DIAGNOSTICS

     sk%d: couldn't map memory	A fatal initialization error has occurred.

     sk%d: couldn't map ports  A fatal initialization error has occurred.

     sk%d: couldn't map interrupt  A fatal initialization error has occurred.

     sk%d: failed to enable memory mapping!  The driver failed to initialize PCI shared memory mapping.  This might happen if the card is not in a
     bus-master slot.

     sk%d: no memory for jumbo buffers!  The driver failed to allocate memory for jumbo frames during initialization.

     sk%d: watchdog timeout  The device has stopped responding to the network, or there is a problem with the network connection (cable).

SEE ALSO

     ifmedia(4), intro(4), netintro(4), pci(4), ifconfig(8)

     XaQti XMAC II datasheet, http://www.xaqti.com.

     SysKonnect GEnesis programming manual, http://www.syskonnect.com.

HISTORY

     The sk device driver first appeared in FreeBSD 3.0.  OpenBSD support was added in OpenBSD 2.6.  NetBSD support was added in NetBSD 2.0.

     The msk driver first appeared in OpenBSD 4.0, and was ported to NetBSD 4.0.

AUTHORS

     The sk driver was written by Bill Paul <wpaul@ctr.columbia.edu>.  Support for the Marvell Yukon-2 was added by Mark Kettenis
     <kettenis@openbsd.org>.

BUGS

     This driver is experimental.

     Support for checksum offload is unimplemented.

     Performance with at least some Marvell-based adapters is poor, especially on loaded PCI buses or when the adapters are behind PCI-PCI
     bridges.  It is believed that this is because the Marvell parts have significantly less buffering than the original SysKonnect cards had.

BSD
								 September 9, 2006							       BSD