________________________________________ From: Mike Galbraith [[email protected]] Sent: Friday, March 21, 2014 9:41 AM To: Davis, Bud @ SSG - Link Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: RE: Bug 71331 - mlock yields processor to lower priority process
On Fri, 2014-03-21 at 14:01 +0000, [email protected] wrote: > If you call mlock () from a SCHED_FIFO task, you expect it to return > when done. You don't expect it to block, and your task to be > pre-empted. Say some of your pages are sitting in an nfs swapfile orbiting Neptune, how do they get home, and what should we do meanwhile? -Mike Two options. #1. Return with a status value of EAGAIN. or #2. Don't return until you can do it. If SCHED_FIFO is used, and mlock() is called, the intention of the user is very clear. Run this task until it is completed or it blocks (and until a bit ago, mlock() did not block). SCHED_FIFO users don't care about fairness. They want the system to do what it is told. regards, Bud Davis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
