sfxge: Do no allow EFSYS_MEM_ALLOC sleep

2014-05-20 Thread Andrew Rybchenko
It solves locking problem when EFSYS_MEM_ALLOC is called in the context holding a mutex (not allowed to sleep). E.g. on interface bring up or multicast addresses addition. sfxge: Do no allow EFSYS_MEM_ALLOC sleep It solves locking problem when EFSYS_MEM_ALLOC is called in the context holding a mu

Re: Problem with ipfw table add 0.0.0.0/8

2014-05-20 Thread Alexander V. Chernikov
On 19.05.2014 17:12, bycn82 wrote: On 5/19/14 21:00, Alexander V. Chernikov wrote: On 19.05.2014 11:51, Bill Yuan wrote: Hi Alex, Hello Bill! You guys are chatting here! I agree with you, the table is the place should be enhanced, and I am working in this way as described below 1. Support

Re: [Was]: Problem with ipfw table add 0.0.0.0/8

2014-05-20 Thread Alexander V. Chernikov
On 19.05.2014 17:38, Dennis Yusupoff wrote: It's not enough, actually. Imagine what you have a table with different networks. If you'll try to find out is an IP belongs to some of that networks from the table, you should to write relatively serious "wrapper" with network range calculations in it.

Re: [Was]: Problem with ipfw table add 0.0.0.0/8

2014-05-20 Thread bycn82
It will e nice to have this utility function > On 21 May, 2014, at 1:32 am, "Alexander V. Chernikov" > wrote: > >> On 19.05.2014 17:38, Dennis Yusupoff wrote: >> It's not enough, actually. >> Imagine what you have a table with different networks. If you'll try to >> find out is an IP belongs to

[rfc] add non-contiguous CPU ID support to in_rss.c

2014-05-20 Thread Adrian Chadd
Hi Robert, This patch uses CPU_FIRST() and CPU_NEXT() to iterate over the CPU IDs. Think this is alright? -a Index: sys/netinet/in_rss.c === --- sys/netinet/in_rss.c (revision 266429) +++ sys/netinet/in_rss.c (working copy) @@ -17