From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "Nish Aravamudan" <nish.aravamudan@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
ptb@inv.it.uc3m.es, "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: sleep under spinlock, sequencer.c, 2.6.12.5
Date: Mon, 22 Aug 2005 17:17:44 +0200 (MET DST) [thread overview]
Message-ID: <200508221517.j7MFHiu10054@inv.it.uc3m.es> (raw)
In-Reply-To: <29495f1d05081917012fbb57aa@mail.gmail.com> from "Nish Aravamudan" at "Aug 19, 2005 05:01:37 pm"
"Also sprach Nish Aravamudan:"
> On 8/19/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Gwe, 2005-08-19 at 10:13 +0200, Peter T. Breuer wrote:
> > > The following "sleep under spinlock" is still present as of linux
> > > 2.6.12.5 in sound/oss/sequencer.c in midi_outc:
> > >
> > >
> > > n = 3 * HZ; /* Timeout */
> > >
> > > spin_lock_irqsave(&lock,flags);
> > > while (n && !midi_devs[dev]->outputc(dev, data)) {
> > > interruptible_sleep_on_timeout(&seq_sleeper, HZ/25);
> > > n--;
> > > }
> > > spin_unlock_irqrestore(&lock,flags);
> > >
> > >
> > > I haven't thought about it, just noted it. It's been there forever
> > > (some others in the sound architecture have been gradually disappearing
> > > as newer kernels come out).
> >
> > Yep thats a blind substition of lock_kernel in an old tree it seems.
> > Probably my fault. Should drop it before the sleep and take it straight
> > after.
>
> Also, the use of n makes no sense. Indicates total sleep for 3
Well spotted.
> seconds, but actually sleep for 40 milliseconds 3*HZ times
> (potentially)?
I presume it should be
n -= HZ/25;
(and "n > 0", of course).
> In any case, probably should be:
>
> timeout = jiffies + 3*HZ;
>
> spin_lock_irqsave(&lock, flags);
> while (time_before(jiffies, timeout) && !midi_devs[dev]->outputc(dev, data)) {
> spin_unlock_irqrestore(&lock, flags);
> interruptible_sleep_on_timeout(&seq_sleeper, msecs_to_jiffies(40));
Well, you'd know. Is there something there really not taken care of by
"HZ"?
> spin_lock_irqsave(&lock, flags);
> }
> spin_lock_irqrestore(&lock, flags);
Peter
next prev parent reply other threads:[~2005-08-22 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 8:13 Peter T. Breuer
2005-08-19 18:07 ` Alan Cox
2005-08-20 0:01 ` Nish Aravamudan
2005-08-22 15:17 ` Peter T. Breuer [this message]
2005-08-22 16:22 ` Nish Aravamudan
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=200508221517.j7MFHiu10054@inv.it.uc3m.es \
--to=ptb@inv.it.uc3m.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®