Something seems to have changed relative to stack memory and asynch
I/O. I used to be able (prior to pre-5) to allocate an AIO structure on
the stack and submit it (blocking of course in the process to pin the
stack). I have seen SMP cases where writes from one processor to the
AIO strcture don't show up when the final callback returns. This would
indicate to me a problem with TLB IPI flushing. In the cases where I am
seeing corruption, this side affect is also present, which results in
corruption (the write does not complete). The two may not be unrelated,
but I could see how a stale cached TLB entry could wreck all kinds of
havoc.
:-)
Jeff
Andrea Arcangeli wrote:
>
> On Tue, 30 May 2000, Jeff V. Merkey wrote:
>
> >asynch I/O directly. I am also seeing write corruption on an NWFS
> >volume in the directory file (i.e. the primary gets written, but the
>
> The elevator race that could trigger with compaq smart and dac960 couldn't
> cause disk corruption.
>
> Andrea
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:27 EST