On Mer, 2005-12-14 at 01:12 -0800, Sridhar Samudrala wrote:
Pass __GFP_CRITICAL flag with all allocation requests that are critical.
- All allocations needed to process incoming packets are marked as CRITICAL.
This includes the allocations
- made by the driver to receive incoming
Alan Cox wrote:
But your user space that would add the routes is not so protected so I'm
not sure this is actually a solution, more of an extended fudge.
Yes, there's no 100% solution -- no matter how much memory you reserve and
how many paths you protect if you try hard enough you can come up
On Wed, 2005-12-14 at 11:17 +, Alan Cox wrote:
On Mer, 2005-12-14 at 01:12 -0800, Sridhar Samudrala wrote:
Pass __GFP_CRITICAL flag with all allocation requests that are critical.
- All allocations needed to process incoming packets are marked as CRITICAL.
This includes the
Sridhar Samudrala wrote:
The only reason i made these macros is that i would expect this to a compile
time configurable option so that there is zero overhead for regular users.
#ifdef CONFIG_CRIT_SOCKET
#define SK_CRIT_ALLOC(sk, flags) ((sk-sk_allocation __GFP_CRITICAL) |
flags)
#define
On Wed, 2005-12-14 at 04:12 -0800, Mitchell Blank Jr wrote:
Alan Cox wrote:
But your user space that would add the routes is not so protected so I'm
not sure this is actually a solution, more of an extended fudge.
Yes, there's no 100% solution -- no matter how much memory you reserve and
