netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: Andi Kleen <ak@suse.de>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
	Donald Becker <becker@scyld.com>,
	netdev@oss.sgi.com
Subject: Re: how to report network device errors to userspace?
Date: 19 Jun 2002 17:45:55 -0400	[thread overview]
Message-ID: <m34rfzq6wb.fsf@trained-monkey.org> (raw)
In-Reply-To: Andi Kleen's message of "Wed, 19 Jun 2002 23:36:59 +0200"

>>>>> "Andi" == Andi Kleen <ak@suse.de> writes:

Andi> On Wed, Jun 19, 2002 at 05:19:14PM -0400, Chris Friesen wrote:
>> Currently the way we are doing it for ethernet is that the
>> userspace app calls a device ioctl() with SIOCGMIIREG multiple
>> times per second, but it would be nice to have the driver notify us
>> asynchronously.

Andi> I would suggest sending a netlink message from the driver.
Andi> That's really what netlink was designed for.

Hmmm, the broader issue here is that we should aim for a generic
interface - if netlink is the way, maybe it would be worth documenting
it and moving towards getting it into more/all drivers.

I have had this question from other sides as well - hadn't thought of
netlink.

Cheers,
Jes

  parent reply	other threads:[~2002-06-19 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 18:39 how to report network device errors to userspace? Chris Friesen
2002-06-19 20:21 ` Donald Becker
2002-06-19 21:19   ` Chris Friesen
2002-06-19 21:36     ` Andi Kleen
2002-06-19 21:44       ` Chris Friesen
2002-06-19 21:54         ` Andi Kleen
2002-06-20  2:44           ` James Morris
2002-06-20  2:50             ` jamal
2002-06-19 21:45       ` Jes Sorensen [this message]
2002-06-19 21:50         ` Chris Friesen

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=m34rfzq6wb.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=ak@suse.de \
    --cc=becker@scyld.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=netdev@oss.sgi.com \
    /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).