Re: Network Stack Locking
From: Robert Watson (rwatson_at_freebsd.org)
Date: 05/26/04
- Previous message: Robert Watson: "Re: Network Stack Locking"
- In reply to: Julian Elischer: "Re: Network Stack Locking"
- Next in thread: Robert Watson: "Re: Network Stack Locking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 26 May 2004 17:28:49 -0400 (EDT) To: Julian Elischer <julian@elischer.org>
On Tue, 25 May 2004, Julian Elischer wrote:
> This is how netgraph works. (particularly in 5.x)
It's also worth pointing out, for those looking at various approaches,
that NetBSD is currently discussing continuation primitives on the
tech-kern mailing list (I seem to have gotten added to the CC line lately,
which I don't object to :-).
You can also argue that things like bio's, PCB's, et al, are
implementations of the continuation philosophy, just lacking a abstracted
primitive. They maintain state to be picked up by a context but
discarding the stack. Callouts and callbacks are used to perform
scheduling, however, rather than the scheduler explicitly.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org Senior Research Scientist, McAfee Research
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Robert Watson: "Re: Network Stack Locking"
- In reply to: Julian Elischer: "Re: Network Stack Locking"
- Next in thread: Robert Watson: "Re: Network Stack Locking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]