From: "chen, xiangping" <chen_xiangping@emc.com>
To: "'Jes Sorensen'" <jes@wildopensource.com>
Cc: "'Steve Whitehouse'" <Steve@ChyGwyn.com>, linux-kernel@vger.kernel.org
Subject: RE: Kernel deadlock using nbd over acenic driver.
Date: Tue, 14 May 2002 12:07:30 -0400 [thread overview]
Message-ID: <FA2F59D0E55B4B4892EA076FF8704F553D1A52@srgraham.eng.emc.com> (raw)
But how to avoid system hangs due to running out of memory?
Is there a safe guide line? Generally slow is tolerable, but
crash is not.
Thanks,
Xiangping
-----Original Message-----
From: Jes Sorensen [mailto:jes@wildopensource.com]
Sent: Tuesday, May 14, 2002 11:11 AM
To: chen, xiangping
Cc: 'Steve Whitehouse'; linux-kernel@vger.kernel.org
Subject: Re: Kernel deadlock using nbd over acenic driver.
>>>>> "Xiangping" == chen, xiangping <chen_xiangping@emc.com> writes:
Xiangping> But the acenic driver author suggested that sndbuf should
Xiangping> be at least 262144, and the sndbuf can not exceed
Xiangping> r/wmem_default. Is that correct?
Ehm, the acenic author is me ;-)
The default value is what all sockets are assigned on open, you can
adjust this using SO_SNDBUF and SO_RCVBUF, however the values you set
cannot exceed the [rw]mem_max values. Basically if you set the default
to 4MB, your telnet sockets will have a 4MB default limit as well
which may not be what you want (not saying it will use 4MB).
Thus, set the _max values and use SO_SNDBUF and SO_RCVBUF to set the
per process values. But leave the _default values to their original
setting.
Xiangping> So for gigabit Ethernet driver, what is the optimal mem
Xiangping> configuration for performance and reliability?
It depends on your application, number of streams, general usage of
the connection etc. There's no perfect-for-all magic number.
Jes
next reply other threads:[~2002-05-14 16:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:07 chen, xiangping [this message]
2002-05-14 16:32 ` Kernel deadlock using nbd over acenic driver Steven Whitehouse
2002-05-14 16:48 ` Alan Cox
2002-05-15 22:31 ` Oliver Xymoron
2002-05-16 5:10 ` Peter T. Breuer
2002-05-16 5:19 ` Peter T. Breuer
2002-05-16 14:29 ` Oliver Xymoron
2002-05-16 15:35 ` Peter T. Breuer
2002-05-16 16:22 ` Oliver Xymoron
2002-05-16 16:45 ` Peter T. Breuer
2002-05-16 16:35 ` Steven Whitehouse
2002-05-17 7:01 ` Peter T. Breuer
2002-05-17 9:26 ` Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 22:54 Peter T. Breuer
2002-05-17 8:44 ` Steven Whitehouse
2002-05-23 13:21 ` Peter T. Breuer
2002-05-24 10:11 ` Steven Whitehouse
2002-05-24 11:43 ` Peter T. Breuer
2002-05-24 13:28 ` Steven Whitehouse
2002-05-24 15:54 ` Peter T. Breuer
2002-05-27 13:04 ` Steven Whitehouse
2002-05-27 19:51 ` Peter T. Breuer
2002-05-27 13:44 ` Pavel Machek
2002-05-29 10:51 ` Peter T. Breuer
2002-05-29 11:21 ` Pavel Machek
2002-05-29 12:10 ` Peter T. Breuer
2002-05-29 13:24 ` Jens Axboe
2002-06-01 21:13 ` Peter T. Breuer
2002-06-05 8:48 ` Steven Whitehouse
2002-06-02 6:39 ` Pavel Machek
[not found] <3CE40A77.22C74DC1@zip.com.au>
2002-05-16 20:28 ` Peter T. Breuer
2002-05-16 13:18 chen, xiangping
2002-05-15 21:43 Peter T. Breuer
2002-05-16 8:33 ` Steven Whitehouse
2002-05-15 17:43 Peter T. Breuer
2002-05-15 19:43 ` Steven Whitehouse
2002-05-16 5:15 ` Peter T. Breuer
2002-05-16 8:04 ` Steven Whitehouse
2002-05-16 8:49 ` Peter T. Breuer
2002-05-15 16:01 Peter T. Breuer
2002-05-14 17:42 chen, xiangping
2002-05-14 17:36 chen, xiangping
2002-05-14 18:02 ` Alan Cox
2002-05-14 15:05 chen, xiangping
2002-05-14 15:11 ` Jes Sorensen
2002-05-10 15:39 chen, xiangping
2002-05-10 15:02 chen, xiangping
2002-05-10 15:11 ` Steven Whitehouse
2002-05-14 14:58 ` Jes Sorensen
2002-05-06 15:05 chen, xiangping
2002-05-07 8:15 ` Steven Whitehouse
2002-05-06 2:26 chen, xiangping
2002-05-06 8:45 ` Steven Whitehouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FA2F59D0E55B4B4892EA076FF8704F553D1A52@srgraham.eng.emc.com \
--to=chen_xiangping@emc.com \
--cc=Steve@ChyGwyn.com \
--cc=jes@wildopensource.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).