public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] udev 016 release
Date: Wed, 04 Feb 2004 01:03:33 +0200	[thread overview]
Message-ID: <1075849413.11322.6.camel@nosferatu.lan> (raw)
In-Reply-To: <1075843712.7473.60.camel@nosferatu.lan>


[-- Attachment #1.1: Type: text/plain, Size: 791 bytes --]

On Tue, 2004-02-03 at 23:28, Martin Schlemmer wrote:
> On Tue, 2004-02-03 at 22:13, Greg KH wrote:
> 
> Except if I miss something major, udevsend and udevd still do not
> work:
> 

Skip that, it does work if SEQNUM is set :P

Anyhow, is it _really_ needed for SEQNUM to be set?  What about
the attached patch?

Then, order I have not really checked yet, but there are two things
that bother me:

1) latency is even higher than before (btw Greg, is there going to be
more sysfs/whatever fixes to get udev even faster, or is this the
limit?)

2) events gets missing.  If you for example use udevsend in the
initscript that populate /dev (/udev), the amount of nodes/links
created is off with about 10-50 (once about 250) entries.


Thanks,


-- 
Martin Schlemmer

[-- Attachment #1.2: udev-016-udevsend-missing-seqnum.patch --]
[-- Type: text/x-patch, Size: 405 bytes --]

--- udev-016/udevsend.c	2004-02-04 00:55:23.522428312 +0200
+++ udev-016.seqnum/udevsend.c	2004-02-04 00:57:37.898000120 +0200
@@ -149,10 +149,14 @@
 
 	seqnum = get_seqnum();
 	if (seqnum == NULL) {
+#if 0
 		dbg("no seqnum");
 		goto exit;
+#endif
+		seq = 1;
+	} else {
+		seq = atoi(seqnum);
 	}
-	seq = atoi(seqnum);
 
 	sock = socket(AF_LOCAL, SOCK_STREAM, 0);
 	if (sock == -1) {

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-03 23:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 20:49 ` Martin Schlemmer
2004-02-03 23:14   ` Greg KH
2004-02-03 21:28 ` Martin Schlemmer
2004-02-03 23:03   ` Martin Schlemmer [this message]
2004-02-03 23:13     ` Greg KH
2004-02-04  0:01       ` Kay Sievers
2004-02-04  4:25       ` Martin Schlemmer
2004-02-08 11:27         ` Martin Schlemmer
2004-02-08 13:01           ` Martin Schlemmer
2004-02-03 21:43 ` Martin Schlemmer
2004-02-11 22:13   ` Greg KH
2004-02-11 22:27     ` Martin Schlemmer
2004-02-12  1:19       ` Greg KH

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=1075849413.11322.6.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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