From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "Stephen Hemminger" <shemminger@osdl.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-aio@kvack.org>
Subject: RE: Race condition between aio_complete and aio_read_evt
Date: Tue, 8 Jul 2003 16:03:07 -0700 [thread overview]
Message-ID: <41F331DBE1178346A6F30D7CF124B24B2A4888@fmsmsx409.fm.intel.com> (raw)
> From: Stephen Hemminger [mailto:shemminger@osdl.org]
> Sent: Tuesday, July 08, 2003 4:00 PM
> Subject: Re: Race condition between aio_complete and aio_read_evt
> Make those smp_* memory barrier's because they don't matter on UP.
Certainly, thanks for pointing that out. I was about to say that as
well.
- Ken
next reply other threads:[~2003-07-08 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 23:03 Chen, Kenneth W [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 21:52 Chen, Kenneth W
2003-07-08 23:00 ` Stephen Hemminger
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=41F331DBE1178346A6F30D7CF124B24B2A4888@fmsmsx409.fm.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@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
all inboxes | Powered by JetHome®