From: Johannes Berg <johannes@sipsolutions.net>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: James Morris <jmorris@namei.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: TCP stalls in current git, possibly splice related
Date: Wed, 18 Jul 2007 00:36:10 +0200 [thread overview]
Message-ID: <1184711770.4658.5.camel@johannes.berg> (raw)
In-Reply-To: <20070716120247.GG5195@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Mon, 2007-07-16 at 14:02 +0200, Jens Axboe wrote:
> Yep, it's a sender thing, so upgrading the receiver will not change
> anything.
Ok, I upgraded, but that didn't help. And in fact, I don't see how it
could have since synergy doesn't use splice or sendfile. I should've
thought of that right away, sorry.
It seems that packets are actually coming in during the time that my
mouse hangs though (ran wireshark in parallel and saw no pauses in the
timeline.) Hence, it actually seems to be on the receiver side, and
running the synergy client under strace reveals that during the time my
mouse hangs it's in poll() waiting for input on the tcp socket. sysrg-t
doesn't show anything useful, it's just scheduling waiting for data.
According to wireshark data is sent, but it never shows up at the
application layer.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-07-18 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 20:12 TCP stalls in current git, possibly splice related James Morris
2007-07-12 20:52 ` David Miller
2007-07-13 2:26 ` James Morris
2007-07-13 5:36 ` Jens Axboe
2007-07-13 6:26 ` Jens Axboe
2007-07-13 9:25 ` Jens Axboe
2007-07-13 10:02 ` Johannes Berg
2007-07-13 11:05 ` Jens Axboe
2007-07-13 12:23 ` James Morris
2007-07-13 21:55 ` Johannes Berg
2007-07-16 8:45 ` Johannes Berg
2007-07-16 12:02 ` Jens Axboe
2007-07-17 22:36 ` Johannes Berg [this message]
2007-07-18 10:49 ` Jens Axboe
2007-07-18 10:58 ` Johannes Berg
2007-07-18 21:24 ` Johannes Berg
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=1184711770.4658.5.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=jens.axboe@oracle.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
/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).