How about something more generic?
Jeff
Van Okamura wrote:
>
> "Jeff V. Merkey" wrote:
>
> > For O_SYNC writes, I am assuming you will be using you the cache in
> > Oracle, and that the O_SYNC case will be used flushing commits. What
> > frequecy of writes vs. reads do you normally exhibit, and what
> > percentage of writes will use the O_SYNC semantic. In my earlier
> > dialogue with Alan, the idea came up to call fsync() (which flushes the
> > cache) after any calls to write() with O_SYNC set in the file handle. I
> > think it would be nice to provide a something less coarse than:
> >
> > write();
> > fsync();
> >
> > Saying performance is critical is cool, but what would you consider
> > would be the best semantic to provide this behavior in a performant
> > manner that would allow Oracle to get best case performance?
>
> Well, Redhat Enterprise Edition implements features like raw i/o,
> vectored i/o, and 64-bit i/o that improve performance. You could look
> at those interfaces for more details.
-
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 : Tue May 23 2000 - 21:00:11 EST