From: Arjan van de Ven <arjanv@redhat.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 4/13] use cpu_relax() in busy loop
Date: Fri, 19 Sep 2003 21:54:12 +0200 [thread overview]
Message-ID: <20030919215412.D22138@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030919124845.A27079@osdlab.pdx.osdl.net>; from chrisw@osdl.org on Fri, Sep 19, 2003 at 12:48:45PM -0700
On Fri, Sep 19, 2003 at 12:48:45PM -0700, Chris Wright wrote:
> * Arjan van de Ven (arjanv@redhat.com) wrote:
> >
> > mdelay ?
>
> Yeah, good point. For these subsecond pauses mdelay() makes more sense.
> It'd be nice to get rid of long busy loops in general.
yep; first step is making them grep-able by using mdelay ;)
next prev parent reply other threads:[~2003-09-19 19:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 23:25 [PATCH 1/13] use cpu_relax() in busy loop Chris Wright
2003-09-18 23:27 ` [PATCH 2/13] " Chris Wright
2003-09-18 23:29 ` [PATCH 3/13] " Chris Wright
2003-09-18 23:31 ` [PATCH 4/13] " Chris Wright
2003-09-18 23:33 ` [PATCH 5/13] " Chris Wright
2003-09-18 23:34 ` [PATCH 6/13] " Chris Wright
2003-09-18 23:35 ` [PATCH 7/13] " Chris Wright
2003-09-18 23:36 ` [PATCH 8/13] " Chris Wright
2003-09-18 23:37 ` [PATCH 9/13] " Chris Wright
2003-09-18 23:40 ` [PATCH 10/13] " Chris Wright
2003-09-18 23:41 ` [PATCH 11/13] " Chris Wright
2003-09-18 23:43 ` [PATCH 12/13] " Chris Wright
2003-09-18 23:46 ` [PATCH 13/13] " Chris Wright
2003-09-20 7:37 ` [PATCH 9/13] " David S. Miller
2003-09-19 7:37 ` [PATCH 7/13] " Arjan van de Ven
2003-09-19 19:49 ` Chris Wright
2003-09-19 7:34 ` [PATCH 4/13] " Arjan van de Ven
2003-09-19 19:48 ` Chris Wright
2003-09-19 19:54 ` Arjan van de Ven [this message]
2003-09-19 7:33 ` [PATCH 2/13] " Arjan van de Ven
2003-09-19 19:49 ` Chris Wright
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=20030919215412.D22138@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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