All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph V Moss <jmoss@ichips.intel.com>
To: David Meleedy <david.meleedy@analog.com>
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: /net support
Date: Tue, 31 Oct 2006 13:00:59 -0800	[thread overview]
Message-ID: <29733.1162328459@ichips.intel.com> (raw)
In-Reply-To: Your message of "Tue, 31 Oct 2006 15:42:11 EST." <200610312042.k9VKgBVw009630@jetcar.spd.analog.com>

> 
> > That very much depends on usage.
> > 
> > If you have a bunch of clients that typically open and load files of
> > potentially several hundred megabytes then UDP retransmits can become a
> > problem.
> > 
> > But then if traffic is light there's not much to be gained and if there
> > are traffic spikes possibly something to be lost.
> 
> Well, our CAD software can generate files varying from several hundred
> megabytes up to 1-3 gigabytes.  So yes, we actually do have
> large files being transmitted, which is why I had been looking at not
> using tcp on the LAN.  But tcp is the only reliable WAN method I've
> found.  I think what I'm going to have to do is generate local NIS
> maps for every client and use a "program" script to read them.  That
> way I can insert the appropriate flags in there, depending on whether
> or not a machine is on the LAN vs. WAN.  I had just noticed that on
> Solaris, the behavior seems to work much better than on linux, so I was
> kind of wondering how they had solved it.

If you're going to be dealing with files that large, then you're probably
better off switching to all TCP, since you can also switch to larger
block sizes.  Try comparing the performance of copying files with
'tcp,rsize=32768,wsize=32768' to your current settings.

  reply	other threads:[~2006-10-31 21:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 20:22 /net support David Meleedy
2006-10-27 23:04 ` Jeff Moyer
2006-10-28  4:05 ` Ian Kent
2006-10-30 22:52   ` David Meleedy
2006-10-30 23:29     ` Jeff Moyer
2006-10-31  0:14       ` David Meleedy
2006-10-31  8:31         ` Ian Kent
2006-10-31 15:04           ` Jeff Moyer
2006-10-31 20:42           ` David Meleedy
2006-10-31 21:00             ` Joseph V Moss [this message]
2006-10-31 21:58               ` David Meleedy
2006-11-01  2:39             ` Ian Kent
2006-11-01 20:32               ` David Meleedy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29733.1162328459@ichips.intel.com \
    --to=jmoss@ichips.intel.com \
    --cc=autofs@linux.kernel.org \
    --cc=david.meleedy@analog.com \
    --cc=raven@themaw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.