From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: [PATCH, RFC] backchannel overflows
Date: Fri, 1 May 2015 10:23:45 -0700 [thread overview]
Message-ID: <20150501172345.GB29624@infradead.org> (raw)
In-Reply-To: <E905ADC8-AB2B-45A7-87FD-0ADF660EA811@oracle.com>
On Thu, Apr 30, 2015 at 01:41:02PM -0400, Chuck Lever wrote:
> We discussed this briefly during the Linux NFS town hall meeting.
> I agree using dynamic slot allocation for TCP is fine, and RPC/RDMA
> can use simple overprovisioning.
>
> This way the upper layer (NFSv4.1 client) doesn?t have to be aware of
> limitations in the RPC layer mechanism.
>
> Trond may have an additional concern that I didn?t capture.
The other option would be to simply overallocate in the transport layer,
as that is the layer which causes the problem to start with.
That being said, what is the argument for doing any sort of static
allocation here? I'm fine with doing fully dynamic allocation if that
works out fine, but a mixed static / dynamic allocation sounds like a
nightmare.
next prev parent reply other threads:[~2015-05-01 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:21 [PATCH, RFC] backchannel overflows Christoph Hellwig
2015-04-29 12:08 ` Kinglong Mee
2015-04-29 13:46 ` Christoph Hellwig
2015-04-29 14:55 ` Chuck Lever
2015-04-29 14:58 ` Trond Myklebust
2015-04-29 15:14 ` Christoph Hellwig
2015-04-29 15:24 ` Trond Myklebust
2015-04-29 17:34 ` J. Bruce Fields
2015-04-30 6:25 ` Christoph Hellwig
2015-04-30 14:34 ` Chuck Lever
2015-04-30 14:37 ` Christoph Hellwig
[not found] ` <CAHQdGtRgEVXidNNYtYf4c3uS0vc6fbm-SZ5AxrY=awXYynmACw@mail.gmail.com>
2015-04-30 15:02 ` Trond Myklebust
2015-04-30 15:11 ` Chuck Lever
2015-04-30 17:41 ` Chuck Lever
2015-05-01 17:23 ` Christoph Hellwig [this message]
2015-05-01 17:28 ` Trond Myklebust
2015-05-01 17:37 ` Christoph Hellwig
2015-05-01 17:47 ` Trond Myklebust
2015-05-01 17:31 ` Chuck Lever
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=20150501172345.GB29624@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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