Thanks!
On Thu, Apr 9, 2020 at 8:29 PM Luigi Rizzo wrote:
> On Thu, Apr 9, 2020 at 2:18 AM Özkan KIRIK wrote:
> >
> > Hello,
> >
> > I wonder if it is possible to update dummynet code multi-threading
> capable
> > practically?
> > My idea is below:
> > - A new sysctl tunable will be defined as
On Thu, Apr 9, 2020 at 2:18 AM Özkan KIRIK wrote:
>
> Hello,
>
> I wonder if it is possible to update dummynet code multi-threading capable
> practically?
> My idea is below:
> - A new sysctl tunable will be defined as
> "net.inet.ip.dummynet.thread_count" (default 1)
> - To distribute tasks along
> In my production environment there are many schedulers and pipes &
> queues belongs to this scheds.
> dummynet uses %90-100 percent of single cpu. (ie. 20 scheds, 30 pipes,
> 35 queues total. Each pipe has max 30-100Mbps)
If the perfomance issue is urgent, you may give netgraph (ng_car, ng_pipe)
In my production environment there are many schedulers and pipes & queues
belongs to this scheds.
dummynet uses %90-100 percent of single cpu. (ie. 20 scheds, 30 pipes, 35
queues total. Each pipe has max 30-100Mbps)
In my idea, by distributing schedulers to different threads, all pipes that
belong
On Thu, Apr 9, 2020 at 2:18 AM Özkan KIRIK wrote:
>
> Hello,
>
> I wonder if it is possible to update dummynet code multi-threading capable
> practically?
> My idea is below:
> - A new sysctl tunable will be defined as
> "net.inet.ip.dummynet.thread_count" (default 1)
> - To distribute tasks along
Hello,
I wonder if it is possible to update dummynet code multi-threading capable
practically?
My idea is below:
- A new sysctl tunable will be defined as
"net.inet.ip.dummynet.thread_count" (default 1)
- To distribute tasks along threads, each sched instance can be assigned to
different thread.
-
