We I have not looked at Robert's recycle skb patch yet. I couldn't find it in the link he sent me so I don't know how it works. However I thought about it a little more and realized that even when y
We I have not looked at Robert's recycle skb patch yet. I couldn't find it in the link he sent me so I don't know how it works. However I thought about it a little more and realized that even when y
Mala, Could you please at least cc netdev on networking related issues? It says so in the kernel FAQ. I swore back around 95 to join lk only when Linux gets a IDE maintainer who is not insane. Hasnt
Jamal wrote .. Yes I will, it is a mistake from my part, Even if I turned the hot list, the slab allocator has a per cpu array of objects. In this case it keeps by default 60 objects and hot list kee
I swore back around 95 to join lk only when Linux gets a IDE maintainer who is not insane. Hasnt happened yet. Alan is now one of the 2.5.x IDE maintainers, would you like me to add you to linux-kern
Well, the hotlist is supposed to be one way to reduce the effect of initialization. Same conclusion as us then standard practise for eons on networking in rtoses at least. Slab on Linux was supposed
Troy Wilson (who works with me) posted SPECweb99 results using my skbinit patch to lkml on Friday: http://www.uwsg.iu.edu/hypermail/linux/kernel/0208.2/1470.html I know you don't subscribe to lkml.
That is true if it is a uni processor but in smp the initialization, if happened in two different CPUs, affects performance due to cache effects. The problem of object (skb) allocation, usage and dea
The posting you pointed to says 1% - not that it matters. It becomes more insignificant when skb recycling comes in play mostly because the alloc and freeing of skbs doesnt really show up as hotlist
Jamal wrote .. SPECweb99 profile shows that __kfree_skb is in the top 5 hot routines. We will test the skb recycle patch on SPECweb99 and add skbinit patch to that and see how it helps. What I unders