Re: NWFS readpage() in 2.2.X -- after_unlock_page() not exported

[Jeff V. Merkey]

call __free_page() after the IO completes seems to be the deal here. 
This is very confusing in the code FYI.

Jeff

"Jeff V. Merkey" wrote:
> 
> "Jeff V. Merkey" wrote:
> >
> 
> Another item that's somewhat confusing in the code is that
> generic_readpage() is FREEING the page by setting PG_free_after in the
> page->flags then calling __free_page() in after_unlock_page() which
> would seem to indicate that right after going through the overhead of
> writing data into the page, we free it after the IO completes (???).
> Doesn't the page with the data we just copied get cached in the page
> cache, or is there yet another copy operation somewhere else?
> 
> What's the deal here?
> 
> Jeff