linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: (interruptible_)sleep_on_timeout question
Date: Thu, 23 May 2002 19:25:33 -0700	[thread overview]
Message-ID: <3CEDA49D.8040001@redswitch.com> (raw)


Hi,

Is it possible to dynamically change the timeout value of
sleep_on_timeout()? I encountered a situation where the timeout value is
got from some interrupt handler, which will modify the value. For example,

main() {
/* the main process goes to sleep with a timeout */
....
interruptible_sleep_on_timeout(q, timeout);
....
}

int_handler() {
      /* If the interrupt happens before timeout, the handler
       * gets a new timeout value and makes the main process
       * continue to sleep.
       */
}

Is it possible to implement this mechanism? I thought about kernel timer
and variation of sleep_on_timeout(). But all seems to have some problems.

Thanks a lot.

Shawn.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2002-05-24  2:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CEDA49D.8040001@redswitch.com \
    --to=xjin@redswitch.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).