linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev hangs under high loads
Date: Mon, 25 Oct 2004 17:07:50 +0000	[thread overview]
Message-ID: <20041025170750.GA31117@vrfy.org> (raw)
In-Reply-To: <20041023054119.GA11915@kroah.com>

On Mon, Oct 25, 2004 at 12:01:04AM -0700, Greg KH wrote:
> On Sun, Oct 24, 2004 at 09:56:16PM +0200, Kay Sievers wrote:
> > On Sun, Oct 24, 2004 at 09:51:01PM +0200, Marco d'Itri wrote:
> > > On Oct 24, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > 
> > > > Just use a "normal" filesysten then and everything is fine.
> > > There are many good reasons for using tmpfs for /dev, and I would be
> > > very displeased if this will not be possible or practical anymore.
> > 
> > Yes it's nice and there is still nothing wrong with tmpfs use. It's just
> > a bit more space needed than before. Ever thought about much memory _every_
> > file in sysfs takes?
> That being said, putting a single, small (less than a single page) file
> for every device node in the system in tmpfs should not be a big deal.
> Anyone have any real numbers that they are worried about?

On my box with app. 800 device nodes (which should be the number of app. 90 percent
of the boxes out there) tmpfs is ~3 MByte big with the files db. That's not cool,
but it's a limitation of tmpfs not udev :)
I personally think the complete independend and reliable operation of concurrent
events is more worth than to work around a filesystem limitation with our own
single-file-db implementation.

The average multi-file-db file is less than 40 Bytes long now. Maybe it will grow
a bit, but not much, as we only need to store the names of our created nodes and the
all_partitions count. Every other information (major/minor, type) can be stat()'ed
from the node itself, we don't need to store it in the db.

The question is: Can we change the tmpfs implementation to store file content
inline if it fits into struct shmem_inode_info. Mostly the same way symlink
targets are handled today (only targets longer than 110 bytes are allocating a page).

This would be much more efficient, uses minimal memory and is the fastest we can get.
And it would solve all the problems, I don't have :)

Thanks,
Kay


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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

  parent reply	other threads:[~2004-10-25 17:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23  5:41 udev hangs under high loads Greg KH
2004-10-23  6:31 ` Kay Sievers
2004-10-24  5:08 ` Kay Sievers
2004-10-24  5:53 ` Olaf Hering
2004-10-24 15:53 ` Kay Sievers
2004-10-24 15:57 ` Olaf Hering
2004-10-24 19:27 ` Kevin P. Fleming
2004-10-24 19:46 ` Kay Sievers
2004-10-24 19:51 ` Marco d'Itri
2004-10-24 19:56 ` Kay Sievers
2004-10-25  2:51 ` Kay Sievers
2004-10-25  7:01 ` Greg KH
2004-10-25 17:07 ` Kay Sievers [this message]
2004-10-25 17:12 ` Kevin P. Fleming
2004-10-25 17:27 ` Nishanth Aravamudan
2004-10-25 17:53 ` Kay Sievers
2004-10-25 20:55 ` Nishanth Aravamudan

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=20041025170750.GA31117@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).