linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-hotplug@vger.kernel.org
Subject: many instances of "/sbin/ifup ethx" coming from udev/hotplug
Date: Tue, 11 Dec 2007 21:45:32 +0000	[thread overview]
Message-ID: <475F04FC.2040802@nortel.com> (raw)


Hi all,

We're running a 2.6.14 kernel and have a situation where multiple (20 or 
so) ethx devices are being created in about 3 seconds.  This appears to 
cause latency issues for other tasks on the system due to all the 
"/sbin/ifup ethx" processes that get created.

We're seeing these processes being created by udevd directly, by 
/sbin/hotplug, and by /etc/sysconfig/network-scripts/net.hotplug (which 
is in turn created by udevd).

Can someone shed some light as to why ifup gets called from three 
different places for the same event, and whether it's expected to cause 
latency issues?  Also, is there anything we can do to streamline this?

Thanks,

Chris

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2007-12-11 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 21:45 Chris Friesen [this message]
2007-12-11 21:53 ` many instances of "/sbin/ifup ethx" coming from udev/hotplug Kay Sievers
2007-12-11 22:10 ` Chris Friesen
2007-12-12  5:42 ` Kay Sievers

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=475F04FC.2040802@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).