Am Dienstag, 28. September 2004 09:56 schrieb Duncan Sands:
> > > Also, is there really any point in monitoring the line status?
> > > That's one thing that could be done perfectly well from user space.
> >
> > It's cheap and easy to do it in the kernel; it doesn't involve running a
> > daemon. Listening to the interrupt endpoint is probably better done in-
> > kernel, I think.
>
> However line monitoring is entirely informative: it's not like the driver needs
> to do anything different if the line goes down. The only point of the monitoring
> is to tell the user that the line went down. So rather than the kernel doing
> the monitoring and using a printk (ugh) or a sysfs/proc/netlink whatever thingy
> to tell user space, doesn't it make more sense to have a little user-space
> utility that monitors the line and takes whatever action it thinks is appropriate?
No, the main user is not user space, but the networking code. All line
monitoring for ethernet is done in kernel space exactly for that reason.
There's a defined interface for reporting line state and it's been there
for ages.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
