mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danek Duvall <duvall@emufarm.org>
To: J Sloan <jjs@lexus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: root-owned /proc/pid files for threaded apps?
Date: Fri, 8 Mar 2002 13:59:08 -0800	[thread overview]
Message-ID: <20020308215908.GB886@lorien.emufarm.org> (raw)
In-Reply-To: <20020307060110.GA303@lorien.emufarm.org> <E16iyBW-0002HP-00@the-village.bc.nu> <20020308100632.GA192@lorien.emufarm.org> <20020308195939.A6295@devcon.net> <20020308203157.GA457@lorien.emufarm.org> <20020308222942.A7163@devcon.net> <3C893171.2050003@lexus.com>
In-Reply-To: <3C893171.2050003@lexus.com>

On Fri, Mar 08, 2002 at 01:47:29PM -0800, J Sloan wrote:

> Andreas Ferber wrote:
> 
> >As a side note, IMHO it would be sensible to have some way of
> >disabling module autoloading of protocol modules in the network stack.
> >
> 
> What is the problem with using modules.conf e.g.
> 
> alias net-pf-10 off

I have that.  The problem is that if every time a program attempts to
make an IPv6 connection it forces the kernel to spawn off modprobe to go
look for it, you have a performance issue.  Of course, I'd imagine that
a reasonably written program would not try to use IPv6 beyond the first
failure.

Danek

      reply	other threads:[~2002-03-08 21:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  6:01 Danek Duvall
2002-03-07  7:43 ` Danek Duvall
2002-03-07 13:43 ` Alan Cox
2002-03-08 10:06   ` Danek Duvall
2002-03-08 13:33     ` Alan Cox
2002-03-08 18:59     ` Andreas Ferber
2002-03-08 20:31       ` Danek Duvall
2002-03-08 21:29         ` Andreas Ferber
2002-03-08 21:41           ` Danek Duvall
2002-03-08 22:30             ` Andreas Ferber
2002-03-09  3:09               ` Danek Duvall
2002-03-10 20:37                 ` Andreas Ferber
2002-03-08 21:47           ` J Sloan
2002-03-08 21:59             ` Danek Duvall [this message]

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=20020308215908.GB886@lorien.emufarm.org \
    --to=duvall@emufarm.org \
    --cc=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®