[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1340291526.4604.5710.camel@edumazet-glaptop>
Date: Thu, 21 Jun 2012 17:12:06 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dmitry Kravkov <dmitry@...adcom.com>
Cc: Tomas Hruby <thruby@...gle.com>,
David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"therbert@...gle.com" <therbert@...gle.com>,
"evansr@...gle.com" <evansr@...gle.com>,
Eilon Greenstein <eilong@...adcom.com>,
Merav Sicron <meravs@...adcom.com>,
Yaniv Rosner <yaniv.rosner@...adcom.com>,
"willemb@...gle.com" <willemb@...gle.com>
Subject: Re: [PATCH] bnx2x: fix panic when TX ring is full
On Thu, 2012-06-21 at 15:19 +0300, Dmitry Kravkov wrote:
> The crash happens with default configuration since
> [4acb41903b2f99f3dffd4c3df9acc84ca5942cb2] "net/tcp: Fix tcp memory
> limits initialization when !CONFIG_SYSCTL", but it can be hit by
> increasing values of tcp_wmem even earlier.
This makes no sense.
> From: Dmitry Kravkov <dmitry@...adcom.com>
> Subject: [PATCH net-next] bnx2x: reservation for NEXT tx BDs
>
> Commit [4acb41903b2f99f3dffd4c3df9acc84ca5942cb2]
> net/tcp: Fix tcp memory limits initialization when !CONFIG_SYSCTL
> provided new default value for tcp_wmem, since heavy tcp
> traffic may cause the TSO packet to consume 20 BDs + 1 for next page
> descriptor.
This is completely bogus. I have no idea how you came to this.
A forwarding workload can trigger same bug, if GRO is enabled.
Remove this wrong bit, please ?
--
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
Powered by blists - more mailing lists