From: Zhangguanghui <zhang.guanghui@h3c.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] o2net_sendpage reviews, thanks
Date: Tue, 30 Jun 2015 03:28:08 +0000 [thread overview]
Message-ID: <2015063011280785381652@h3c.com> (raw)
In-Reply-To: 2015063011180600247349@h3c.com
Hi
1. In the callback o2net_sendpage -> sendpage()
2. If sendpage (tcp socket send) continuously returns -EAGAIN, then get into an endless loop,
even though the function of cond_resched() have already used.
3. I think it is not reasonable, try to continuously send 20 times returns -EAGAIN ,
shutdown the socket to avoid affecting the entire cluster.
Finally, any feedback about this process (positive or negative) would be greatly appreciated.
--- tcp.c 2015-06-30 11:46:54.727447919 +0800
+++ tcp.c.diff 2015-06-30 11:52:12.823447881 +0800
@@ -949,6 +949,7 @@
{
struct o2net_node *nn = o2net_nn_from_num(sc->sc_node->nd_num);
ssize_t ret;
+ int send_fails = 20;
while (1) {
mutex_lock(&sc->sc_send_lock);
@@ -959,10 +960,11 @@
mutex_unlock(&sc->sc_send_lock);
if (ret == size)
break;
- if (ret == (ssize_t)-EAGAIN) {
+ if (ret == (ssize_t)-EAGAIN && send_fails > 0) {
mlog(0, "sendpage of size %zu to " SC_NODEF_FMT
" returned EAGAIN\n", size, SC_NODEF_ARGS(sc));
cond_resched();
+ --send_fails;
continue;
}
mlog(ML_ERROR, "sendpage of size %zu to " SC_NODEF_FMT
syslog:
/var/log/syslog:Jun 29 09:32:58 cvk47 kernel: [156022.769539] (kworker/u130:1,12041,9):o2net_sendpage:1026 sendpage of size 24 to node cvk61 (num 5) at 172.16.202.61:7100 returned EAGAINne
/var/log/syslog:Jun 29 09:32:58 cvk47 kernel: [156022.769542] (kworker/u130:1,12041,9):o2net_sendpage:1026 sendpage of size 24 to node cvk61 (num 5) at 172.16.202.61:7100 returned EAGAINne
/var/log/syslog:Jun 29 09:32:58 cvk47 kernel: [156022.769544] (kworker/u130:1,12041,9):o2net_sendpage:1026 sendpage of size 24 to node cvk61 (num 5) at 172.16.202.61:7100 returned EAGAINne
/var/log/syslog:Jun 29 09:32:58 cvk47 kernel: [156022.769546] (kworker/u130:1,12041,9):o2net_sendpage:1026 sendpage of
________________________________
zhangguanghui 10102
-------------------------------------------------------------------------------------------------------------------------------------
????????????????????????????????????????
????????????????????????????????????????
????????????????????????????????????????
???
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20150630/e3d5e240/attachment-0001.html
prev parent reply other threads:[~2015-06-30 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 13:06 [Ocfs2-devel] o2net_tx_can_proceed reviews, thanks Zhangguanghui
2015-06-07 0:27 ` Joseph Qi
2015-06-30 3:13 ` [Ocfs2-devel] o2net_sendpage " Zhangguanghui
2015-06-30 3:18 ` Zhangguanghui
2015-06-30 3:28 ` Zhangguanghui [this message]
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=2015063011280785381652@h3c.com \
--to=zhang.guanghui@h3c.com \
--cc=ocfs2-devel@oss.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 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.