From: "J. Bruce Fields" <bfields@fieldses.org>
To: Manjunath Patil <manjunath.b.patil@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] nfsd: return ENOSPC if unable to allocate a session slot
Date: Sun, 24 Jun 2018 16:26:15 -0400 [thread overview]
Message-ID: <20180624202615.GA31496@fieldses.org> (raw)
In-Reply-To: <20180622175416.GA7119@fieldses.org>
By the way, could you share some more details with us about the
situation when you (or your customers) are actually hitting this case?
How many clients, what kind of clients, etc. And what version of the
server were you seeing the problem on? (I'm mainly curious whether
de766e570413 and 44d8660d3bb0 were already applied.)
I'm glad we're thinking about how to handle this case, but my feeling is
that the server is probably just being *much* too conservative about
these allocations, and the most important thing may be to fix that and
make it a lot rarer that we hit this case in the first place.
--b.
next prev parent reply other threads:[~2018-06-24 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:35 [PATCH 1/2] nfsv4: handle ENOSPC during create session Manjunath Patil
2018-06-21 16:35 ` [PATCH 2/2] nfsd: return ENOSPC if unable to allocate a session slot Manjunath Patil
2018-06-22 17:54 ` J. Bruce Fields
2018-06-22 21:49 ` Chuck Lever
2018-06-22 22:31 ` Trond Myklebust
2018-06-22 23:10 ` Trond Myklebust
2018-06-23 19:00 ` Chuck Lever
2018-06-24 13:56 ` Trond Myklebust
2018-06-25 15:39 ` Chuck Lever
2018-06-25 16:45 ` Trond Myklebust
2018-06-25 17:03 ` Manjunath Patil
2018-06-24 20:26 ` J. Bruce Fields [this message]
[not found] ` <bde64edc-5684-82d7-4488-e2ebdd7018fc@oracle.com>
2018-06-25 22:04 ` J. Bruce Fields
2018-06-26 17:20 ` Manjunath Patil
2018-07-09 14:25 ` J. Bruce Fields
2018-07-09 21:57 ` Trond Myklebust
2018-06-21 17:04 ` [PATCH 1/2] nfsv4: handle ENOSPC during create session Trond Myklebust
2018-06-22 14:28 ` Manjunath Patil
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=20180624202615.GA31496@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=manjunath.b.patil@oracle.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).