* should "get_user_pages()" really be phased out?
@ 2016-01-04 19:01 Robert P. J. Day
0 siblings, 0 replies; only message in thread
From: Robert P. J. Day @ 2016-01-04 19:01 UTC (permalink / raw)
To: kernelnewbies
poking around mm/gup.c at "get_user_pages()" and related routines,
and noticed this:
* get_user_pages should be phased out in favor of
* get_user_pages_locked|unlocked or get_user_pages_fast. Nothing
* should use get_user_pages because it cannot pass
* FAULT_FLAG_ALLOW_RETRY to handle_mm_fault.
so does that mean what it seems to mean ... that nothing outside of
memory management should call get_user_pages() directly? i can see
that some of those other routines are implemented in terms of
get_user_pages() -- does that mean that get_user_pages() should be
made static so that only those routines are allowed to call it, and
everyone else should invoke one of the other routines?
just trying to understand the eventual desired fate of
get_user_pages().
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-01-04 19:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-04 19:01 should "get_user_pages()" really be phased out? Robert P. J. Day
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.