Re: FILE_NO_INTERMEDIATE_BUFFERING & FILE_APPEND_DATA

Thanks David, thanks for your excellent explanation. :slight_smile:

2009/1/24 David Craig

> I would say that comment is misleading at best. I would say ‘cannot’ is
> probably best replaced with ‘should not’. At the storage stack, no driver
> knows that the read or write requests being processed are for a file that
> is
> not buffered. That also doesn’t include controllers and/or drives that
> contain internal caches where Windows has no way to tell those devices not
> to cache data.
>
> Now as to your question, look at CreateFile in user land. Read the
> restrictions on block and offset values. Allowing append data would
> require
> that the file end at the correct boundary, so I guess they don’t permit
> them
> to be combined.
>
> wrote in message news:xxxxx@ntfsd…
> > Hi, guys.
> >
> > I read this from wdk document:
> >
> > “FILE_NO_INTERMEDIATE_BUFFERING :
> > The file cannot be cached or buffered in a driver’s internal buffers.
> > This flag is incompatible with the DesiredAccess FILE_APPEND_DATA flag.”
> >
> > Why is these two flags incompatible?
> >
> > Thanks in advance!
> >
>
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>