netdev - Re: [PATCH V3 net-next] neigh: new unresolved queue limits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1320837029.2315.24.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date:	Wed, 09 Nov 2011 12:10:29 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH V3 net-next] neigh: new unresolved queue limits

Le mercredi 09 novembre 2011 à 12:04 +0100, Eric Dumazet a écrit :
> unres_qlen is the number of frames we are able to queue per unresolved
> neighbour. Its default value (3) was never changed and is responsible
> for strange drops, especially if IP fragments are used, or multiple
> sessions start in parallel. Even a single tcp flow can hit this limit.
> 

> Signed-off-by: Eric Dumazet <eric.dumazet@...il.com>

Oh well I forgot the missing bit :

 [NDTPA_QUEUE_LENBYTES]          = { .type = NLA_U32 },

I am sending a V4 ASAP


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html