From: Steven Whitehouse <steve@gw.chygwyn.com>
To: chen_xiangping@emc.com (chen, xiangping)
Cc: linux-kernel@vger.kernel.org
Subject: Re: The memory usage of the network block device
Date: Sat, 17 Nov 2001 10:27:30 +0000 (GMT) [thread overview]
Message-ID: <200111171027.KAA18835@gw.chygwyn.com> (raw)
In-Reply-To: <FA2F59D0E55B4B4892EA076FF8704F553D1891@srgraham.eng.emc.com> from "chen, xiangping" at Nov 16, 2001 03:44:48 PM
Hi,
>
> Hi,
>
> I changed a setup to make the server response quicker, and the
> client slower. Looks OK now. So the problem seems like too many
> pending tcp requests stucks the client system. Is there any good
> way to control the flow or pending requests of the system? I
> tried to set some threshold in do_nbd_requests, only blocks the
> processes in _get_request_wait() which is not I wanted.
>
> Thanks,
>
> Xiangping
>
>
I did wonder about that whih was why I asked the question about the tcp_*mem
settings. I guess that if that is the case either you can increase the tcp_*mem
settings or make the maximum number of blocks merged into a single request
lower. Personally I'd go for the former solution, all you need to do is select
suitable numbers to set for these files (see
linux/Documentation/networking/ip-sysctl.txt for their exact meaning). If
this does turn out to be the problem, then you'll need to make the config
changes on both server and client as they can both send maximum sized requests
(128 (MAX_SEGMENTS) sectors plus the size of the header).
To reduce the request size you can alter MAX_SEGMENTS in blkdev.h but this
isn't really a very good solution as it reduces the ability to merge I/O
for local disks.
Steve.
next prev parent reply other threads:[~2001-11-17 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 20:44 chen, xiangping
2001-11-17 10:27 ` Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 14:41 chen, xiangping
2001-11-16 4:20 chen, xiangping
2001-11-16 10:16 ` 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=200111171027.KAA18835@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=chen_xiangping@emc.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
all inboxes | Powered by JetHome®