From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 14 May 2002 10:58:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 14 May 2002 10:58:45 -0400 Received: from trained-monkey.org ([209.217.122.11]:44043 "EHLO trained-monkey.org") by vger.kernel.org with ESMTP id ; Tue, 14 May 2002 10:58:44 -0400 To: "chen, xiangping" Cc: "'Steve Whitehouse'" , linux-kernel@vger.kernel.org Subject: Re: Kernel deadlock using nbd over acenic driver. In-Reply-To: From: Jes Sorensen Date: 14 May 2002 10:58:43 -0400 Message-ID: X-Mailer: Gnus v5.7/Emacs 20.7 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "xiangping" == chen, xiangping writes: xiangping> Hi, When the system stucks, I could not get any response xiangping> from the console or terminal. But basically the only xiangping> network connections on both machine are the nbd connection xiangping> and a couple of telnet sessions. That is what shows on xiangping> "netstat -t". xiangping> /proc/sys/net/ipv4/tcp_[rw]mem are "4096 262144 4096000", xiangping> /proc/sys/net/core/*mem_default are 4096000, xiangping> /proc/sys/net/core/*mem_max are 8192000, I did not change xiangping> /proc/sys/net/ipv4/tcp_mem. Don't do this, setting the [rw]mem_default values to that is just insane. Do it in the applications that needs it and nowhere else. xiangping> The system was low in memory, I started up 20 to 40 thread xiangping> to do block write simultaneously. If you have a lot of outstanding connections and active threads, it's not unlikely you run out of memory if each socket eats 4MB. Jes