From: Arjan van de Ven <arjanv@redhat.com>
To: Rainer Keller <Keller@hlrs.de>, linux-kernel@vger.kernel.org
Subject: Re: Small optimizations for UP (sched and prefetch)
Date: Thu, 10 Jan 2002 10:57:07 +0000 [thread overview]
Message-ID: <3C3D7383.9F45013@redhat.com> (raw)
In-Reply-To: <3C3D6582.576A3D8D@hlrs.de>
> +
> +#ifndef CONFIG_SMP
> +#define spin_lock_prefetch(x)
> +#else
> +#define spin_lock_prefetch(x) prefetchw(x)
> +#endif
>
please make it
+#define spin_lock_prefetch(x) do {} while (0)
instead of an empty define...
prev parent reply other threads:[~2002-01-10 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 9:57 Small optimizations for UP (sched and prefetch) Rainer Keller
2002-01-10 10:57 ` Arjan van de Ven [this message]
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=3C3D7383.9F45013@redhat.com \
--to=arjanv@redhat.com \
--cc=Keller@hlrs.de \
--cc=linux-kernel@vger.kernel.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