Re: [chrony-dev] [PATCH] sys_posix: support SCHED_FIFO and mlockall on more OSs |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [PATCH] sys_posix: support SCHED_FIFO and mlockall on more OSs
- From: "Stefan R. Filipek" <srfilipek@xxxxxxxxx>
- Date: Tue, 16 Apr 2019 08:14:30 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Lu9VsE4ZLxoa0NPU30LXMDCFAvoF8TkoXgmfTwzR+LU=; b=U7pL+31NmHNSYP2iXRJ7IMj7BEqUYBV+/0DDzbSGGFEVrAWnWEVJ0MwclEt0R45ZlN K7lsEr/0Oy8CgQKEOQ80tDeK+UljCYtaH+OwdcUD/n3zGIOSAipKfw3KhNgh0xqZ43ZE btX+yE9Qt2EjbNq/QFpRUXXiCZyiQBP3WvpLMz4iBguBjgCodPTNSIDgrvWEl8LuAoY6 FfseZEDCJagNfi88ldXmFBtC4kx7OaIR3Mlb2Rh6tYLoCzYzE2L6BCelxHWvsGaGq4Tl kXfWJmRTWL8VMVLkcN2UYXoDmzw1Z3zXZe75Ys4+PZ2vAEwUKiYRXMRzORFth8qub06c rU9Q==
Thanks for the feedback.
> Could that not lead into situations where chronyd randomly fails later after start when it needs to allocate more memory?
With MCL_FUTURE specified, yes it could fail. The thought was to just
abide by the previously set system limits (assuming that is why it
failed), but that would cause more problems than its worth. I'll
revert the behavior.
With Solaris, since it does not have this artificial limit, we should
be safe to use mlockall by itself (according to my understanding of
the docs).
>> + add_def POSIX
> I don't like this definition very much.
I didn't either, but I wasn't sure what the preferred style would be.
I'll change the conditional calls to check for supported platforms
individually.
> it's a good opportunity to update the coding style to match the majority of the code
I'll do what I can, but please fill in the gaps on the final patch.
> As for sending the patches, have you tried git send-email? That should avoid problems with formatting.
Maybe one day I'll learn how to copy and paste patches out of a
terminal and into gmail. In the mean time, I'll try your suggestion.
Regards,
Stefan
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.