From: Jeff Garzik <jgarzik@pobox.com>
To: domen@coderock.org
Cc: netdev@oss.sgi.com, nacc@us.ibm.com
Subject: Re: [patch 14/26] net/slip: replace schedule_timeout() with msleep()
Date: Tue, 22 Mar 2005 18:59:14 -0500 [thread overview]
Message-ID: <4240B152.4080904@pobox.com> (raw)
In-Reply-To: <20050306103322.857041F203@trashy.coderock.org>
domen@coderock.org wrote:
> Use msleep() instead of schedule_timeout() to guarantee
> the task delays as expected. While the original code does use
> TASK_INTERRUPTIBLE, it does not check for signals, so I believe msleep() is more
> appropriate.
>
> Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> Signed-off-by: Domen Puncer <domen@coderock.org>
> ---
>
>
> kj-domen/drivers/net/slip.c | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
>
> diff -puN drivers/net/slip.c~msleep-drivers_net_slip drivers/net/slip.c
> --- kj/drivers/net/slip.c~msleep-drivers_net_slip 2005-03-05 16:10:49.000000000 +0100
> +++ kj-domen/drivers/net/slip.c 2005-03-05 16:10:49.000000000 +0100
> @@ -75,6 +75,7 @@
> #include <linux/if_arp.h>
> #include <linux/if_slip.h>
> #include <linux/init.h>
> +#include <linux/delay.h>
> #include "slip.h"
> #ifdef CONFIG_INET
> #include <linux/ip.h>
> @@ -1395,10 +1396,8 @@ static void __exit slip_exit(void)
> /* First of all: check for active disciplines and hangup them.
> */
> do {
> - if (busy) {
> - set_current_state(TASK_INTERRUPTIBLE);
> - schedule_timeout(HZ / 10);
> - }
> + if (busy)
> + msleep(100);
msleep_interruptible
next prev parent reply other threads:[~2005-03-22 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 10:33 [patch 14/26] net/slip: replace schedule_timeout() with msleep() domen
2005-03-22 23:59 ` Jeff Garzik [this message]
2005-03-23 17:28 ` Nishanth 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=4240B152.4080904@pobox.com \
--to=jgarzik@pobox.com \
--cc=domen@coderock.org \
--cc=nacc@us.ibm.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).