Re: [PATCH] Inbound Connection Control mechanism: Prioritized Accept

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> There are couple of reasons why prioritization in kernel works better than at 
> user level. 
> * The kernel mechanisms are more efficient and scalable than the user space
>   mechanism. Non compliant connection requests are discarded earlier reducing the
>   queuing time of the compliant requests, in particular less CPU is consumed and
>   the context switch to userspace is avoided. 

Im not sure this is that true. I just added a user space implementation to
thttpd to favour one network range and close under load on others to keep
capacity there. Its a ten minute hack, and Im still seeing the same 1400
hits per second or so I was before.

Alan
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux