Messages in this thread | | | Date | Sat, 28 Jan 2006 23:59:07 +0100 | From | Pavel Machek <> | Subject | Re: [patch 3/9] mempool - Make mempools NUMA aware |
| |
Hi!
> >If sending routines can work with constant ammount of memory, why use > >kmalloc at all? Anyway I thought we were talking receiving side > >earlier in the thread. > > > >Ouch and wait a moment. You claim that GFP_KERNEL allocations can't > >block/sleep? Of course they can, that's why they are GFP_KERNEL and > >not GFP_ATOMIC. > > > I didn't meant GFP_KERNEL allocations cannot block/sleep? When in > emergency, we > want even the GFP_KERNEL allocations that are made by critical sockets > not to block/sleep. > So my original critical sockets patches changes the gfp flag passed to > these allocation requests > to GFP_KERNEL|GFP_CRITICAL.
Could we get description of what you are really trying to achieve? I don't know what "critical socket" is, when you are "in emergency", etc. When I am in emergency, I just dial 112...
[Having enough memory on the send side will not mean you'll be able to send data at TCP layer.]
You seem to have some rather strange needs, that are maybe best served by s/GFP_KERNEL/GFP_ATOMIC/ in network layer; but we can't / don't want to do that in vanilla kernel -- your case is too specialized for that. (Ouch and it does not work anyway without rewriting network stack...) Pavel -- Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |