From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] The Ubuntu Collection: Winter/Spring 2006
Date: Fri, 10 Feb 2006 01:35:47 +0000 [thread overview]
Message-ID: <1139535347.17150.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1139525024.17150.22.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Fri, 2006-02-10 at 01:30 +0000, Scott James Remnant wrote:
> On Thu, 2006-02-09 at 23:52 +0100, Marco d'Itri wrote:
>
> > On Feb 09, Scott James Remnant <scott@ubuntu.com> wrote:
> >
> > > The theory is that another udev process will do the opposite, and
> > > both renames will succeed.
> > Did you consider the case of a system with a dozen of interfaces, the
> > exaustion of available udevd child processes and the possible deadlock?
> >
> They'll die off eventually under the three minute rule; if systems with
> dozens of interfaces are really doing this kind of renaming frenzy,
> they're probably doomed anyway :-)
>
Uh, missed the following paragraph ...
This is why it renames the interfaces to a temporary name before
waiting, so there's never a chain deadlock. You'd need a system with
twice the number of interfaces as there were maximum udev processes,
with every single one needing renaming and swapping, and be unlucky
enough for all the wrong ones to be queued at the same time.
I suspect if a sysadmin really reached that, their box is powerful
enough to increase the number of udev children *anyway*.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-10 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 22:43 [PATCH] The Ubuntu Collection: Winter/Spring 2006 Scott James Remnant
2006-02-09 22:52 ` Marco d'Itri
2006-02-10 1:30 ` Scott James Remnant
2006-02-10 1:35 ` Scott James Remnant [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=1139535347.17150.30.camel@localhost.localdomain \
--to=scott@ubuntu.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).