Re: O_DIRECT architecture (was Re: info point on linux hdr)

2000-04-18 Thread Stephen C. Tweedie
Hi, On Tue, Apr 18, 2000 at 01:17:52PM -0500, Steve Lord wrote: > So I guess the question here is how do you plan on keeping track of the > origin of the pages? You don't have to. > Which ones were originally part of the kernel cache > and thus need copying up to user space? If the caller req

Re: O_DIRECT architecture (was Re: info point on linux hdr)

2000-04-18 Thread Steve Lord
> Hi, > > On Tue, Apr 18, 2000 at 07:56:04AM -0500, Steve Lord wrote: > > > I said basic implementation because it is currently paying no attention > > to cached data. The Irix approach to this was to flush or toss cached > > data which overlapped a direct I/O, I am leaning towards keeping them

Re: O_DIRECT architecture (was Re: info point on linux hdr)

2000-04-18 Thread Stephen C. Tweedie
Hi, On Tue, Apr 18, 2000 at 07:56:04AM -0500, Steve Lord wrote: > > XFS is using the pagebuf code we wrote (or I should say are writing - it > needs a lot of work yet). This uses kiobufs to represent data in a set of > pages. So, we have the infrastructure to take a kiobuf and read or write > it

Re: O_DIRECT architecture (was Re: info point on linux hdr)

2000-04-18 Thread Steve Lord
> Hi, > > On Mon, Apr 17, 2000 at 05:58:48PM -0500, Steve Lord wrote: > > > > O_DIRECT on Linux XFS is still a work in progress, we only have > > direct reads so far. A very basic implementation was made available > > this weekend. > > Care to elaborate on how you are doing O_DIRECT? XFS is u