From: Olaf Kirch <okir@suse.de>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Shantanu Goel <sgoel01@yahoo.com>, nfs@lists.sourceforge.net
Subject: Re: [PATCH 2.6.3] Add write throttling to NFS client
Date: Thu, 26 Feb 2004 09:41:46 +0100 [thread overview]
Message-ID: <20040226084146.GA1197@suse.de> (raw)
In-Reply-To: <403D692D.33C4D7E8@melbourne.sgi.com>
On Thu, Feb 26, 2004 at 02:34:05PM +1100, Greg Banks wrote:
> change the allocation algorithm of rpc_rqsts to divide the
> RPC_MAXREQS space into three fixed spaces by class: sync calls,
> async (writes & commits), and all other async calls. Attempts to
I don't think this is a good solution for UDP. If you bump the number
of slots at the same time, you may still end up with the same symptoms,
as your async write requests may eat your congestion window, leaving just
the crumbs for sync requests. If you don't bump the number of slots,
write throughput will suffer.
What about modifying __rpc_sleep_on to put sync tasks always
at the head of the queue? This way sync tasks get priority when
it comes to call reservation.
(for fairness reasons, you may want to walk the queue and insert
your sync task before the first async task at least)
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-02-26 8:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 2:22 [PATCH 2.6.3] Add write throttling to NFS client Shantanu Goel
2004-02-26 3:34 ` Greg Banks
2004-02-26 4:10 ` Shantanu Goel
2004-02-26 8:41 ` Olaf Kirch [this message]
2004-02-26 12:49 ` trond.myklebust
2004-02-26 13:20 ` Bogdan Costescu
2004-02-26 13:40 ` trond.myklebust
2004-02-26 14:50 ` Olaf Kirch
2004-02-26 16:24 ` Bogdan Costescu
2004-02-26 16:16 ` Bogdan Costescu
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 3:19 Shantanu Goel
2004-02-26 17:22 Lever, Charles
2004-02-26 19:18 ` Bogdan Costescu
[not found] <20040301043316.69563.qmail@web12822.mail.yahoo.com>
2004-03-01 5:50 ` trond.myklebust
2004-03-01 6:52 Lever, Charles
[not found] <20040301065511.29682.qmail@web12824.mail.yahoo.com>
2004-03-01 7:49 ` trond.myklebust
[not found] <20040301081456.37082.qmail@web12823.mail.yahoo.com>
2004-03-01 17:38 ` trond.myklebust
[not found] ` <40437AE4.4030407@lehman.com>
2004-03-01 18:18 ` Bogdan Costescu
2004-03-01 18:58 ` trond.myklebust
[not found] ` <35345.207.214.87.84.1078167489.squirrel@webmail.uio.no>
2004-03-02 0:49 ` trond.myklebust
2004-03-01 18:48 ` trond.myklebust
[not found] ` <404387DD.5010205@lehman.com>
2004-03-01 19:03 ` trond.myklebust
[not found] <20040303032213.58494.qmail@web12823.mail.yahoo.com>
[not found] ` <40461CCC.5040609@lehman.com>
2004-03-03 18:35 ` Trond Myklebust
[not found] ` <40462D4C.1060006@lehman.com>
2004-03-03 23:27 ` Trond Myklebust
[not found] <20040303235442.31317.qmail@web12826.mail.yahoo.com>
2004-03-04 0:18 ` Trond Myklebust
2004-03-05 2:22 ` Trond Myklebust
2004-03-04 2:08 Lever, Charles
2004-03-04 2:13 ` Trond Myklebust
[not found] <20040306021648.85080.qmail@web12824.mail.yahoo.com>
2004-03-06 3:42 ` Trond Myklebust
[not found] <20040306035627.79190.qmail@web12822.mail.yahoo.com>
2004-03-06 4:15 ` Trond Myklebust
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=20040226084146.GA1197@suse.de \
--to=okir@suse.de \
--cc=gnb@melbourne.sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=sgoel01@yahoo.com \
/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.