public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Aaron Sethman <androsyn@ratbox.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	pwaechtler@loewe-komp.de, austin@digitalroadkill.net
Subject: Re: RT Sigio broken on 2.4.19-pre8
Date: Mon, 27 May 2002 20:25:11 -0700	[thread overview]
Message-ID: <3CF2F897.EF17FB0E@kegel.com> (raw)
In-Reply-To: <3CF2D86C.8745D791@kegel.com> <3CF2DCDE.CCBB499F@kegel.com>

Aaron Sethman wrote:
> > > > > > Using the Dan Kegel's Poller_bench utility I noticed that RT SIGIO is not
> > > > > > working on 2.4.19-pre8.  Basically sigtimedwait() is always returning
> > > > > > SIGIO.  Note that 2.4.18 works fine.
> > > > > > ... It seems rtsig-nr keeping rising slowly as the system runs.
> > >
> > > That sounds like the way I'm clearing the signal queue is not working.
> > > Here's a minimal test case for clearing the signal queue.  Could
> > > you try it and tell me what it says?
>
> Just tried the corrected version, still passed.

I can't reproduce the problem here.  

What version of dkftpbench are you using?  What parameters?
Can you send me your kernel .config file?

I did notice and fix an embarassing problem in Poller_bench of 
dkftpbench-0.42; it aborted when Poller_sigio sent its initial readiness
notification (it's spurious, but programs are supposed to
be able to handle that).  Fix is at 
http://www.kegel.com/dkftpbench/pb.patch

Thanks,
Dan

  parent reply	other threads:[~2002-05-28  3:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28  1:07 RT Sigio broken on 2.4.19-pre8 Dan Kegel
2002-05-28  1:26 ` Dan Kegel
2002-05-28  2:06   ` Aaron Sethman
2002-05-28  3:25   ` Dan Kegel [this message]
2002-05-28  2:04 ` Aaron Sethman
  -- strict thread matches above, loose matches on Subject: below --
2002-05-25  8:40 Aaron Sethman
2002-05-25  8:56 ` Aaron Sethman
2002-05-27  8:25 ` Peter Wächtler
2002-05-27  8:34   ` Austin Gonyou
2002-05-27 17:51   ` Aaron Sethman

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=3CF2F897.EF17FB0E@kegel.com \
    --to=dank@kegel.com \
    --cc=androsyn@ratbox.org \
    --cc=austin@digitalroadkill.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwaechtler@loewe-komp.de \
    /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