From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: New driver "sfc" for Solarstorm SFC4000 controller.
Date: Tue, 6 May 2008 07:24:42 -0700 [thread overview]
Message-ID: <20080506072442.82a834c8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080506125008.GA2217@solarflare.com>
On Tue, 6 May 2008 13:50:09 +0100 Ben Hutchings <bhutchings@solarflare.com> wrote:
> Andrew Morton wrote:
> > On Fri, 2 May 2008 17:05:35 +0100 Ben Hutchings <bhutchings@solarflare.com> wrote:
> >
> > > > Oh dear, it found
> > > >
> > > > #5617: FILE: drivers/net/sfc/falcon.c:1877:
> > > > + if (*(volatile u32 *)dma_done == FALCON_STATS_DONE)
> > > >
> > > > which was naughty of you. Perhaps this was already discussed in review
> > > > with the people who actually know what they're talking about.
> > >
> > > There wasn't any specific discussion of this. Is it wrong? We want to
> > > prevent the compiler from caching *dma_done, which is itself written by DMA.
> >
> > Documentation/volatile-considered-harmful.txt has some dicussion.
>
> Looks like we should be using something like:
>
> while (*dma_done != FALCON_STATS_DONE)
> cpu_relax();
>
> But then how do we time-out?
Dunno, something like
while (*dma_done != FALCON_STATS_DONE) {
if (time_after(jiffies, when_to_timeout))
goto timeout;
cpu_relax();
}
or
while (*dma_done != FALCON_STATS_DONE) {
udelay(1);
if (++timeout > TIMEOUT)
goto timeout;
}
?
next prev parent reply other threads:[~2008-05-06 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804301925.m3UJPc72001651@hera.kernel.org>
2008-05-01 19:08 ` New driver "sfc" for Solarstorm SFC4000 controller Andrew Morton
2008-05-02 16:05 ` Ben Hutchings
2008-05-02 18:09 ` Andrew Morton
2008-05-06 12:50 ` Ben Hutchings
2008-05-06 14:24 ` Andrew Morton [this message]
2008-05-06 15:04 ` Ben Hutchings
2008-05-06 15:12 ` Andrew Morton
2008-05-06 15:40 ` Ben Hutchings
2008-05-07 17:55 ` Ben Hutchings
2008-05-02 19:10 ` Michael Brown
2008-05-03 20:01 ` Ben Hutchings
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=20080506072442.82a834c8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).