On Fri, Mar 13, 2015 at 2:36 AM, Meyer Lansky <marku...@inbox.ru> wrote:
> Hello all > continue to study the scheduler is O(1) there was one difficulty with the > string 2 on 3, in that these blocking occurs after lines? > a reference to the code that study - > http://lxr.free-electrons.com/source/kernel/sched.c?v=2.6.36 > what I learn on line 4682 to 4695. > > 1 rcu_read_lock(); > 2 pcred = __task_cred(p); > 3 match = (cred->euid == pcred->euid || > cred->euid == pcread->uid); > 4 rcu_read_unlock(); > > I ask because in the comments there is not described. > Thank. > > Hi I am not clear about your question. perhaps specifically you asked about why rcu_read_lock() is called? > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
