public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Greg Banks <gnb@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: bdflush/rpciod high CPU utilization, profile does not make sense
Date: Mon, 11 Apr 2005 16:41:27 +0200	[thread overview]
Message-ID: <20050411144127.GE13369@unthought.net> (raw)
In-Reply-To: <1113230125.9962.7.camel@lade.trondhjem.org>

On Mon, Apr 11, 2005 at 10:35:25AM -0400, Trond Myklebust wrote:
> må den 11.04.2005 Klokka 15:47 (+0200) skreiv Jakob Oestergaard:
> 
> > Certainly;
> > 
> > http://unthought.net/binary.dmp.bz2
> > 
> > I got an 'invalid snaplen' with the 90000 you suggested, the above dump
> > is done with 9000 - if you need another snaplen please just let me know.
> 
> So, the RPC itself looks good, but it also looks as if after a while you
> are running into some heavy retransmission problems with TCP too (at the
> TCP level now, instead of at the RPC level). When you get into that
> mode, it looks as if every 2nd or 3rd TCP segment being sent from the
> client is being lost...

Odd...

I'm really sorry for using your time if this ends up being just a
networking problem.

> That can mean either that the server is dropping fragments, or that the
> client is dropping the replies. Can you generate a similar tcpdump on
> the server?

Certainly;  http://unthought.net/sparrow.dmp.bz2


-- 

 / jakob


  reply	other threads:[~2005-04-11 14:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 16:01 bdflush/rpciod high CPU utilization, profile does not make sense Jakob Oestergaard
2005-04-06 21:28 ` Trond Myklebust
2005-04-07 15:28   ` Jakob Oestergaard
2005-04-06 23:19 ` Greg Banks
2005-04-07 15:38   ` Jakob Oestergaard
2005-04-07 16:01     ` Greg Banks
2005-04-07 16:17     ` Trond Myklebust
2005-04-09 21:35       ` Jakob Oestergaard
2005-04-09 21:52         ` Trond Myklebust
2005-04-11  7:48           ` Jakob Oestergaard
2005-04-11 12:35             ` Trond Myklebust
2005-04-11 13:47               ` Jakob Oestergaard
2005-04-11 14:35                 ` Trond Myklebust
2005-04-11 14:41                   ` Jakob Oestergaard [this message]
2005-04-11 15:21                     ` Trond Myklebust
2005-04-11 15:42                       ` Jakob Oestergaard
2005-04-12  1:03                         ` Greg Banks
2005-04-12  9:28                           ` Jakob Oestergaard
2005-04-19 19:45                             ` Jakob Oestergaard
2005-04-19 22:46                               ` Trond Myklebust
2005-04-20 13:57                                 ` Jakob Oestergaard
2005-04-24  7:15                                   ` Jakob Oestergaard
2005-04-25  3:09                                     ` Trond Myklebust
2005-04-25 13:50                                       ` Jakob Oestergaard

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=20050411144127.GE13369@unthought.net \
    --to=jakob@unthought.net \
    --cc=gnb@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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