|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 1/2] tools/xenstore: set oom score for xenstore daemon on Linux
Juergen Gross writes ("Re: [PATCH v3 1/2] tools/xenstore: set oom score for
xenstore daemon on Linux"):
> Correct. Otherwise the user would need to know about the oom_score_adj
> ABI.
I think they might know about it. In particular, sysadmins might well
be used to configuring this directly (for other daemons).
> On 30.07.21 15:26, Ian Jackson wrote:
> > But maybe we could add something to the doc comment ?
> >
> > Eg
> > # (The specified value is multiplied by -10 and echoed into
> > # /proc/PID/oom_score_adj.)
> >
> > ?
>
> Why? This is an internal implementation detail. I don't see why the
> user needs to know how this is accomplished. What is unclear with the
> XENSTORED_OOM_MEM_THRESHOLD semantics as described?
The underlying interface is both also-publicly-exposed, and has a
nonobvious mapping. Speaking as a sometime sysadmin, I would often
appreciate something like this.
> There is no other parameter with an explanation how it's semantics are
> being accomplished.
I don't think the other parameters are as strange as this.
Ian.
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |