From: Steve Dickson <SteveD@RedHat.com>
To: MINOURA Makoto <minoura@valinux.co.jp>
Cc: nfs@lists.sourceforge.net, taka@valinux.co.jp, yamamoto@valinux.co.jp
Subject: Re: NFSD Flow Control Using the TCP Transport
Date: Tue, 25 Mar 2003 06:33:18 -0500 [thread overview]
Message-ID: <3E803E7E.7040303@RedHat.com> (raw)
In-Reply-To: <20030325053205.1627C1DA3E6@brer.local.valinux.co.jp>
MINOURA Makoto wrote:
>We do not start processing a request (enqueue the socket)
>before we get enough write space for any single request.
>
Right.... This is exactly what is happening. Three or four responses are
*not* being enqueued because there is not enough write space. The
problem I'm seeing is those sockets are never getting re-enqueued.
Your patch is depending on the tcp layer calling svc_write_space()
[when the write space is freed] to start the enqueuing of the sockets.
For some reason that is not happening in my case.....
SteveD.
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-25 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 15:05 NFSD Flow Control Using the TCP Transport Steve Dickson
2003-03-20 4:24 ` MINOURA Makoto
2003-03-20 4:43 ` MINOURA Makoto
2003-03-21 20:38 ` Steve Dickson
2003-03-24 2:51 ` MINOURA Makoto
2003-03-24 15:07 ` Steve Dickson
2003-03-25 5:32 ` MINOURA Makoto
2003-03-25 11:33 ` Steve Dickson [this message]
2003-03-26 5:07 ` MINOURA Makoto
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=3E803E7E.7040303@RedHat.com \
--to=steved@redhat.com \
--cc=minoura@valinux.co.jp \
--cc=nfs@lists.sourceforge.net \
--cc=taka@valinux.co.jp \
--cc=yamamoto@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.