From: Harald Hoyer <harald@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev cause of disk IO slowdown?
Date: Tue, 25 May 2004 10:21:00 +0000 [thread overview]
Message-ID: <40B31E0C.2080602@redhat.com> (raw)
In-Reply-To: <20040525093923.GC26696@y-boda.hpc2n.umu.se>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
this sounds completly bogus :) a device node is a device node...
Ake wrote:
> Hi!
> I'm experiencing something that looks like a severe slowdown of disk IO
> when going through udev (compared to when going through devfs handled
> /dev). Interrupts and context switches goes up by a factor of 4 when
> removing background noise.
>
> Has anyone seen this?
>
> This is a debian 2.6.5 kernel with udev 0.24 from debian.
> Using devfs mounted /dev i get around 90-100MB/s from /dev/sdb doing
> dd if=/dev/sdb of=/dev/null bs=8192k
> but using udev as /dev handler i get only 15MB/s
>
> The devfs vs udev change is the ONLY difference here (guaranteed).
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2004-05-25 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 9:39 Udev cause of disk IO slowdown? Ake
2004-05-25 10:21 ` Harald Hoyer [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=40B31E0C.2080602@redhat.com \
--to=harald@redhat.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).