I have a question regarding the backlog (size) in 2.0.35. In
browsing through net/core/dev.c (around line 521) we see this code
fragment:
/*
* Check that we aren't overdoing things.
*/
if (!backlog_size)
dropping = 0;
else if (backlog_size > 300)
dropping = 1;
if (dropping)
{
kfree_skb(skb, FREE_READ);
return;
}
The number "300" appears to be sole proprietor controlling the size we
allow the backlog to grow before dropping. Is this number in some way
magical, or is it safe to fiddle with? Ultimately, I'm trying to appraise
a kernel patch which replaces the magic number 300 with a function that
returns a dynamically changing max backlog value based on available memory.
I'm hoping someone (perhaps Alan) can comment further.
cheers,
-bp
-- B. James Phillippe . bryan@terran.org UNIX Software Engineer . http://www.terran.org/~bryan Member since 1.1.59 . finger:bryan@earth.terran.org MOTM: Waiting for the DSL to go in :)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/