Re: Multiple netgraph threads
- From: Hans Petter Selasky <hselasky@xxxxxxx>
- Date: Sun, 30 Mar 2008 11:14:42 +0200
Hi,
Have you thought about nodes that lock the same mutex must be run on the same
thread else for example one thread will run while another will just waits for
a mutex ?
You can achieve this by grouping nodes into a tree, and the node at the top of
the tree decides on which thread the nodes in the tree should be run.
How does your patch handle this ?
Also see recent discussion about multithreaded callouts
on "freebsd-arch@xxxxxxxxxxx". Subject "timeout/callout small step forward".
--HPS
On Sunday 30 March 2008, Alexander Motin wrote:
Hi._______________________________________________
I have implemented a patch (for the HEAD) making netgraph to use several
own threads for event queues processing instead of using single swinet.
It should significantly improve netgraph SMP scalability on complicated
workloads that require queueing by implementation (PPTP/L2TP) or stack
size limitations. It works perfectly on my UP system, showing results
close to original or even a bit better. I have no real SMP test server
to measure real scalability, but test on HTT CPU works fine, utilizing
both virtual cores at the predictable level.
Reviews and feedbacks are welcome.
URL: http://people.freebsd.org/~mav/netgraph.threads.patch
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Multiple netgraph threads
- From: Alexander Motin
- Re: Multiple netgraph threads
- References:
- Multiple netgraph threads
- From: Alexander Motin
- Multiple netgraph threads
- Prev by Date: Re: Multiple netgraph threads
- Next by Date: Re: 7.0 - ifconfig create is not working as expected?
- Previous by thread: Multiple netgraph threads
- Next by thread: Re: Multiple netgraph threads
- Index(es):
Relevant Pages
|
|
