Re: in-kernel tcp server

Nicolas Cormier wrote:
On 6/20/07, John Polstra <jdp@xxxxxxxxxxx> wrote:
Using ng_ksocket is almost the same as using the so* functions, since
the ksocket methods call the so* functions. But by using netgraph, you
get a nice management interface, too.

For my application, I found that going through the socket layer (the so*
functions and/or ng_ksocket) hurt performance too much. That's why I
ended up bypassing them.

Thanks for this precision.

I would actually like to address the performance issues.

is there any chance the oldest version (4.x based) might be released,
or at least it would be nice to get the code snippet that attaches to eh ng_ksocket and
reads and writes the stream..

I could make a TCP ECHO node that way and use it for tracking down the bottlenecks
I'm not too interested in the actual webserver itself.


_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: in-kernel tcp server
    ... Nicolas Cormier wrote: ... the ksocket methods call the so* functions. ... But by using netgraph, you get a nice management interface, too. ...
    (freebsd-hackers)
  • Re: in-kernel tcp server
    ... On 6/20/07, John Polstra wrote: ... the ksocket methods call the so* functions. ... But by using netgraph, you ... get a nice management interface, ...
    (freebsd-hackers)
  • Re: in-kernel tcp server
    ... On 6/20/07, John Polstra wrote: ... >> I'm trying to write a little tcp-server kernel module. ... >> just one thread which talks about netgraph. ... Nicolas Cormier ...
    (freebsd-hackers)
  • Re: in-kernel tcp server
    ... But by using netgraph, you ... >> get a nice management interface, ... I found that going through the socket layer (the so* ... I could make a TCP ECHO node that way and use it for tracking down the bottlenecks ...
    (freebsd-hackers)