Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4378411ybb; Tue, 7 Apr 2020 06:25:40 -0700 (PDT) X-Google-Smtp-Source: APiQypJ/tHLUmWOte9FvppojKX8sW1afTcUltPna8uDbwEDnNe5h5UGHdt4fmlBkcRyyV+QpO/CZ X-Received: by 2002:aca:d50f:: with SMTP id m15mr1753214oig.19.1586265940488; Tue, 07 Apr 2020 06:25:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586265940; cv=none; d=google.com; s=arc-20160816; b=X5DKxTwHfG7EYCq1HiyhMaGpfg/ohwn0iMDqZ3TEaY5G+SPHLTvdRhbxXITvBn6k+M PT1B9LSuAvaRq4Y1sUwGjc8wPlKTshhq3lgb4xBfOOifYNlNlKKpitVVQ6Bxe1vLY+Ud da2NV8Ua4tCatufsPRg+OgTWkEmNWoLwD2OeuMLOLHdMYT1RIpAizm8hsBLY0aZl6zPL 4E/+jtfiOm0xn0HSSQWuvt/7QFrwnAkHgfJpGJPlYl8KluhEfXG0fUP/xeHfBDzeHtUp 9BoFhrtOnzY9Z6Ps/aknfITVMVlf3KwPfHMPQf1UMW5Ghq9u6nUKxu8dAQyMUTLatkKK 7/yQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:mime-version:user-agent:date:message-id:subject :from:to:cc:dkim-signature; bh=iFpX0wEUvG52BzZ7ywOElH5HPg69y7nY2lI1Z/4058E=; b=HFvWib5YuuW5CXzjwE2rY8StqbmfOE5xp3FT0TXu1K46bw4fPxLhIg8LEu/s+Ljw4B qOft2Ity8El+LpLUqNF+08MI+tTVDnjtLx/JTWdkL5GCHBBHwvIUW7LCJDqFA6kYloCA Gav3s5vLfmrWOgvtvW0LATTszYg5eiU48MDwP2LUKK2iL6TgsmOlAtmV4NAsZqXZtvt6 FM+DaPUaxx2pyXjjTJmToGNAV7cm//F+8Ut+R5SIra/d7JaNO0F4IYJWMJ145N/AFYPa YNQJbfQrtBoegEYrYVJaGftKfBEJlDzm58yxAfoX0efO7T+NDvidpQoV7rUyKMARzefR 7+fA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=cacTnPy9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w73si646199oiw.206.2020.04.07.06.25.26; Tue, 07 Apr 2020 06:25:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=cacTnPy9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728862AbgDGNYU (ORCPT + 99 others); Tue, 7 Apr 2020 09:24:20 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:45140 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728812AbgDGNYT (ORCPT ); Tue, 7 Apr 2020 09:24:19 -0400 Received: by mail-wr1-f68.google.com with SMTP id v5so3827536wrp.12; Tue, 07 Apr 2020 06:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=cc:to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=iFpX0wEUvG52BzZ7ywOElH5HPg69y7nY2lI1Z/4058E=; b=cacTnPy9+5VyruFofPGDS0EkZviISlV1JLgdCFMNWCTpqByHnXd4lVH/kyeuVfLuSk bvfNyGjEuGNVoPPya49tYtz6EtEShONcF0OqQvA0jeDctqOz8xa6q1yeNrRr3qEBL9Yh 7hvfipzfk9hO1Q2MMqweAdpW9NWnPS7Ctl66BdiytK7u/WPq4TYsaTRiiRcIBHgKr2Gc jipBHrYGOu5bQ8UeOkEZNKg1o9zAEuSwBVvqxyIBjhV7w29T3EELxn/WomGImtGt/izp MhSg1MC8ORnwARxJmrdcZPAV74njOwM0/cZ469gCEQuNB5lHGl4uVHIEqnn27ptt3naf F7Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:cc:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=iFpX0wEUvG52BzZ7ywOElH5HPg69y7nY2lI1Z/4058E=; b=sPgER/gmhT4IgVZNVeT5DDpH9uBJcmXYLWc9e5ka5kjXzAjSCyLW87uzqKB0WTSkqJ gWYCAd2oe6NpfsVj5LYtrZpi4TIGO7aCcAXc5+ZAjocxHNEHUKphHQTacAs6F3bq1vU8 Kri0lIJWvOMtbBd9ivzstCGAWdJnSHadlCOg9NhEh+8+HZHDjzm5GMukLimqbetVghFV cwBH5cY1vSInPE9xCF6+vYNr325J3y3VDtL+Zpz5PU99M0WPgQqYY0nLqGOMhN0QtMeP nVj5PkQ6zrTuc6aW/UlHMX/h/Uyg17YCsMGgHnRWLisa34GMzp9k49z1fRqJG/CIESnM mStQ== X-Gm-Message-State: AGi0PuYThowVWyAU3JmWt1/leAA2IS3FRbwv4j2gij9SQapzQxqnIPjB sgQAJQOWOmaw2UHBUd2tt0Y= X-Received: by 2002:adf:e282:: with SMTP id v2mr2772924wri.329.1586265857555; Tue, 07 Apr 2020 06:24:17 -0700 (PDT) Received: from ?IPv6:2001:a61:2482:101:3351:6160:8173:cc31? ([2001:a61:2482:101:3351:6160:8173:cc31]) by smtp.gmail.com with ESMTPSA id c11sm5696030wrt.24.2020.04.07.06.24.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Apr 2020 06:24:16 -0700 (PDT) Cc: mtk.manpages@gmail.com, Linux API , lkml , Containers , Christian Brauner , "Eric W. Biederman" , Dmitry Safonov <0x7f454c46@gmail.com>, Andrey Vagin , Adrian Reber , Thomas Gleixner , Andy Lutomirski To: Andrey Vagin , Dmitry Safonov From: "Michael Kerrisk (man-pages)" Subject: A further though on /proc/PID/timens_offsets Message-ID: <703440af-031c-16b5-c1ff-54fb4bb5e10c@gmail.com> Date: Tue, 7 Apr 2020 15:24:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Dmitry, Andrei, Quoting the draft time_namespaces manual page: Associated with each time namespace are offsets, expressed with respect to the initial time namespace, that define the values of the monotonic and boot-time clocks in that namespace. These off‐ sets are exposed via the file /proc/PID/timens_offsets. Within this file, the offsets are expressed as lines consisting of three space-delimited fields: The clock-id identifies the clock whose offsets are being shown. This field is either 1, for CLOCK_MONOTONIC, or 7, for CLOCK_BOOT‐ TIME. What was the reason for exposing numeric clock IDs in the timens_offsets file? In API terms, that seems a little ugly. I think it would have been much nicer if the clocks were defined symbolically in this file. I.e., that reading the file would have shown something like monotonic x y boottime x y And that records similarly with symbolic clock names could have been written to the file. Was there a reason not to do this? Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/