All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Fletcher Mattox <fletcher+autofs@cs.utexas.edu>
Cc: autofs@linux.kernel.org
Subject: Re: autofs illustrations
Date: Tue, 07 Nov 2006 15:40:03 -0500	[thread overview]
Message-ID: <4550EF23.4050901@redhat.com> (raw)
In-Reply-To: <200611071719.kA7HJSvl002639@cs.utexas.edu>

Fletcher Mattox wrote:
> Jeff Moyer writes:
>
>   
>> http://people.redhat.com/jmoyer/autofs_linux_kongress.pdf
>>     
>
> Jeff,
>
> Nice paper.  Thanks!  I'm suffering from RPC port exhaustion (you
> responded to one of my queries last week), so I am especially interested
> in your section on port allocation.  You state
>
> 	When a service requests an RPC connection, binding to
> 	a reserved port is the default.  The RPC layer scans
> 	ports starting from 800 down until it finds one that
> 	is unallocated.
>
> My experience is that the 2.6.17.4 kernel allocates between 512 and 1024
> and then begins with unreserved ports >33000.  Yeah, I know.  It's just
> a nit, but I thought I'd tell you anyway.
>
> The most interesting part of the paper was the comment about a practical
> limit of 100 mounts in rapid succession.  I am certain this is the limit
> we have bumped into.  Do you see any improvement in this in autofs 5?
>
> Unprivileged ports and/or UDP are not viable options for us, so I am
> forced to increase the timeout from 5 minutes to 24 hours, which in
> practice means they are always mounted.  We have about 400 automounted
> filesystems, so the only long term solution for us is to try to coalesce
> them to less than 100.  Very painful.

You have 400 automounted file systems, all of which need to be mounted at
the same time?  If so, I might suggest that static mounts might better serve
your needs.  Or, rethink the application and deployment.

    Thanx...

       ps

  reply	other threads:[~2006-11-07 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 22:37 autofs illustrations wengang wang
2006-11-07  0:10 ` Jeff Moyer
2006-11-07 17:19   ` Fletcher Mattox
2006-11-07 20:40     ` Peter Staubach [this message]
2006-11-07 21:24       ` Fletcher Mattox
2006-11-08 13:29         ` Peter Staubach
2006-11-08 16:38           ` Jeff Moyer
2006-11-08 15:32       ` Michael Blandford
2006-11-08  3:59     ` Ian Kent
2006-11-08 13:25       ` Peter Staubach
2006-11-08 14:00         ` Ian Kent
2006-11-08 22:34           ` Joe Pruett
2006-11-08 23:03             ` Jeff Moyer
2006-11-09  0:37               ` Peter Staubach

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=4550EF23.4050901@redhat.com \
    --to=staubach@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=fletcher+autofs@cs.utexas.edu \
    /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.