lkml.org 
[lkml]   [2015]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [FYI] tux3: Core changes
Date
On Monday, May 25, 2015 9:25:44 PM PDT, Rik van Riel wrote:
> On 05/21/2015 03:53 PM, Daniel Phillips wrote:
>> On Wednesday, May 20, 2015 8:51:46 PM PDT, David Lang wrote:
>>> how do you prevent it from continuing to interact with the old version
>>> of the page and never see updates or have it's changes reflected on
>>> the current page?
>>
>> Why would it do that, and what would be surprising about it? Did
>> you have a specific case in mind?
>
> After a get_page(), page_cache_get(), or other equivalent
> function, a piece of code has the expectation that it can
> continue using that page until after it has released the
> reference count.
>
> This can be an arbitrarily long period of time.

It is perfectly welcome to keep using that page as long as it
wants, Tux3 does not care. When it lets go of the last reference
(and Tux3 has finished with it) then the page is freeable. Did
you have a more specific example where this would be an issue?
Are you talking about kernel or userspace code?

Regards,

Daniel



\
 
 \ /
  Last update: 2015-05-26 07:21    [W:1.126 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site