From: Harshula <harshula@redhat.com>
To: andros@netapp.com
Cc: trond.myklebust@netapp.com, jlayton@redhat.com,
linux-nfs@vger.kernel.org
Subject: Re: [RFC V2 0/1] SUNRPC: dynamic rpc_slot allocator
Date: Wed, 28 Sep 2011 13:08:13 +1000 [thread overview]
Message-ID: <1317179295.2609.2.camel@serendib> (raw)
In-Reply-To: <1305059200-412-1-git-send-email-andros@netapp.com>
Hi Andy,
What's the status of your dynamic slot allocator patch?
cya,
#
On Tue, 2011-05-10 at 16:26 -0400, andros@netapp.com wrote:
> Second version. Responded to comments.
> As for the first version, I would appreciate comments on this patch.
>
> Changes:
>
> - kmalloc instead of mempools
> - same dynamic allocator used by all interested transports.
> - used GFP_ATOMIC for rpc_xprt and initial slot allocation
> - UDP also uses dynamic allocation, but not in response to write_space callback.
> - BC_TCP slots reduced to RPC_MIN_SLOT_TABLE. (could add dynamic if so desired)
>
> See patch comments for more description.
>
> The 10G test bed is not yet configured. I did test with VMs, copying a large
> file over NFSv3/v4. For tcp, started with 2 slots, ended with 7. for udp (same
> file), started with 2 slots, ended with 3.
>
> -->Andy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-28 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 20:26 [RFC V2 0/1] SUNRPC: dynamic rpc_slot allocator andros
2011-05-10 20:26 ` [RFC V2 1/1] " andros
2011-05-18 14:39 ` Jeff Layton
2011-05-18 19:13 ` William A. (Andy) Adamson
2011-09-28 3:08 ` Harshula [this message]
2011-09-28 3:24 ` [RFC V2 0/1] " Myklebust, Trond
2011-09-29 18:15 ` Andy Adamson
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=1317179295.2609.2.camel@serendib \
--to=harshula@redhat.com \
--cc=andros@netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.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 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).