Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Nov 2002 12:48:07 -0800 (PST)
From:      Julian Elischer <julian@elischer.org>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        myevmenk@exodus.net, current@FreeBSD.ORG, net@FreeBSD.ORG
Subject:   Re: Netgraph and KQUEUE(2)
Message-ID:  <Pine.BSF.4.21.0211061245450.726-100000@InterJet.elischer.org>
In-Reply-To: <20021106.125555.20031393.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Wed, 6 Nov 2002, M. Warner Losh wrote:

> In message: <Pine.BSF.4.21.0211060942270.1013-100000@InterJet.elischer.org>
>             Julian Elischer <julian@elischer.org> writes:
> : 
> : 
> : On Wed, 6 Nov 2002, M. Warner Losh wrote:
> : 
> : > : 1) Device driver in Netgraph node. When hardware is
> : > :    activated new Netgraph node is created and new
> : > :    kevent sent. devd (or something like devd) listens
> : > :    for these events and does something (loads firmware,
> : > :    activates device, etc.)
> : > 
> : > Device drivers are not netgraph nodes.  They will have a device_t
> : > associated with them, which already sends a message via /dev/devctl to
> : > devd.  You can do anything you want with the results.  There's no need
> : > to reinvent the wheel that I'm almost done inventing.  There's
> : > absolutely no need to bring netgraph into it all, and doing so makes
> : > it a less generic implementation.
> : 
> : devices that are netgraph nodes may not have any entry in /dev
> : and might only appear in  the netgraph namespace..
> : e.g. if_ar.c if_sr.c
> 
> It doesn't matter.  *ALL* devices have device_t entries.  Recall that
> device_t is not dev_t.  dev_t appears in /dev/.  Hardware devices have
> to attach to some bus.  That's why devd is done in newbus land rather
> than in dev_t land.

Ok but there cound be netgraph nodes that have no hardware but could be
called into creation by some external event.
e.g. a netgraph hook on a pseudointerface like gif or tun.
(not at present but a possibility I was looking at last week)

> 
> Warner
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0211061245450.726-100000>