From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Neil Brown <neilb@suse.com>
Cc: linux-nfs@vger.kernel.org
Subject: RE: [PATCH] SUNRPC: handle -EAGAIN from socket writes better.
Date: Fri, 3 Jul 2015 09:49:37 -0400 [thread overview]
Message-ID: <1435931379-6654-1-git-send-email-trond.myklebust@primarydata.com> (raw)
In-Reply-To: <20150629142623.5afc0e6d@noble>
Hi Neil,
There should already be a handler for ENOBUFS in call_status, but
I can see that it has a couple of flaws. What say we try to fix that
instead?
Cheers
Trond
--
2.4.3
next prev parent reply other threads:[~2015-07-03 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 4:26 [PATCH] SUNRPC: handle -EAGAIN from socket writes better NeilBrown
2015-07-03 13:49 ` Trond Myklebust [this message]
2015-07-03 13:49 ` [PATCH 1/2] SUNRPC: Don't reencode message if transmission failed with ENOBUFS Trond Myklebust
2015-07-03 13:49 ` [PATCH 2/2] SUNRPC: Don't confuse ENOBUFS with a write_space issue Trond Myklebust
2015-07-06 1:26 ` [PATCH] SUNRPC: handle -EAGAIN from socket writes better NeilBrown
2015-07-06 13:36 ` Trond Myklebust
2015-07-07 21:01 ` NeilBrown
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=1435931379-6654-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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