[lustre-devel] lctl conf_param vs set_param -P

Christopher J. Morrone morrone2 at llnl.gov
Tue Aug 18 11:00:23 PDT 2015

On 08/17/2015 08:37 PM, Nathan Rutman wrote:
> The goal of set_param -P (permanent, global) was to replace conf_param
> and harmonize with set_param (local). (conf_param semantics were the
> beginning of an aborted attempt to move away from /proc and toward a
> more rational parameter space.) Unfortunately, most of the conf_param
> items were "specials", that had to be re-implemented under set_param -P.
> Most of that work was done years ago, but some things like "jobid" were
> not around then -- and apparently were implemented using the older
> mechanism only.

Could you elaborate on how jobid is special?  Why, set_param -P not 
currently knowing that jobid is special, is it not simply triggering the 
upcall on all nodes to write a value to the proc file?

How would a system administrator know which things are special and which 
are not, and how the behavior changes for special and non-special options?


More information about the lustre-devel mailing list