From: Mel Gorman <mgorman@suse.de>
To: Sage Weil <sage@inktank.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ceph-devel@vger.kernel.org,
neilb@suse.de, a.p.zijlstra@chello.nl, michaelc@cs.wisc.edu,
emunson@mgebm.net, eric.dumazet@gmail.com,
sebastian@breakpoint.cc, cl@linux.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: regression with poll(2)
Date: Tue, 21 Aug 2012 08:05:15 +0100 [thread overview]
Message-ID: <20120821070515.GA1657@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1208200930510.26904@cobra.newdream.net>
On Mon, Aug 20, 2012 at 09:54:59AM -0700, Sage Weil wrote:
> > <SNIP>
> >
> > > I've retested several times and confirmed that this change leads to the
> > > breakage, and also confirmed that reverting it on top of -rc1 also fixes
> > > the problem.
> > >
> > > I've also added some additional instrumentation to my code and confirmed
> > > that the process is blocking on poll(2) while netstat is reporting
> > > data available on the socket.
> > >
> > > What can I do to help track this down?
> > >
> >
> > Can the following patch be tested please? It is reported to fix an fio
> > regression that may be similar to what you are experiencing but has not
> > been picked up yet.
>
> This patch appears to resolve things for me as well, at least after a
> couple of passes. I'll let you know if I see any further problems come up
> with more testing.
>
Thanks very much Sage.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-08-21 7:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 19:46 regression with poll(2)? Sage Weil
2012-08-15 20:45 ` Atchley, Scott
2012-08-15 21:03 ` Sage Weil
2012-08-19 18:49 ` regression with poll(2) Sage Weil
2012-08-20 8:07 ` Eric Dumazet
2012-08-20 9:04 ` Mel Gorman
2012-08-20 9:30 ` Eric Dumazet
2012-08-20 23:20 ` Andrew Morton
2012-08-21 5:16 ` Eric Dumazet
2012-08-20 16:54 ` Sage Weil
2012-08-21 7:05 ` Mel Gorman [this message]
2012-08-20 17:02 ` Linus Torvalds
2012-08-21 15:58 ` Andrew Morton
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=20120821070515.GA1657@suse.de \
--to=mgorman@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ceph-devel@vger.kernel.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=emunson@mgebm.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=sage@inktank.com \
--cc=sebastian@breakpoint.cc \
--cc=torvalds@linux-foundation.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).