Date: Sun, 1 Jul 2001 03:51:10 +0000 (GMT) From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net> To: Alfred Perlstein <bright@sneakerz.org> Cc: "Michael C . Wu" <keichii@peorth.iteration.net>, freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Quick question: AIO / SMP / process-based threading Message-ID: <Pine.LNX.4.20.0107010345230.29177-100000@www.everquick.net> In-Reply-To: <20010630222829.E84523@sneakerz.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Sat, 30 Jun 2001 22:28:29 -0500 > From: Alfred Perlstein <bright@sneakerz.org> > > Can you point to some specific PRs about this or crashdumps before > (or at least while) taking pot shots at the AIO implementation? In the mean time, until somebody can substantiate that claim... is AIO SMP safe? I see that aiocb.aio_buf is declared as "volatile", so I would presume so. I just want to be sure that, if an aio call runs on one CPU, another CPU can access *aio_buf and be 100% certain that the data are coherent. aio_buf = mmap() using MAP_HASSEMAPHORE -- good idea, bad idea, pointless? TIA, Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet Division Phone: +1 (316) 794-8922 Wichita/(Inter)national Phone: +1 (785) 865-5885 Lawrence --------------------------------------------------------------------------- Date: Mon, 21 May 2001 11:23:58 +0000 (GMT) From: A Trap <blacklist@brics.com> To: blacklist@brics.com Subject: Please ignore this portion of my mail signature. These last few lines are a trap for address-harvesting spambots. Do NOT send mail to <blacklist@brics.com>, or you are likely to be blocked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.20.0107010345230.29177-100000>