All of lore.kernel.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v5 2/4] man/man5/tunables.conf: Document system-wide tunables config
Date: Thu, 06 Aug 2026 23:25:29 -0400	[thread overview]
Message-ID: <xntsp6393q.fsf@greed.delorie.com> (raw)
In-Reply-To: <anUbLZzOLY2qM6iP@devuan> (message from Alejandro Colomar on Fri, 7 Aug 2026 02:06:57 +0200)

Alejandro Colomar <alx@kernel.org> writes:
> Hmmmmm, let's say you call execve(2) several times without any fork(2)s.
> Assuming a that the program paths that you pass to execve(2) are all
> dynamic ELF programs built with glibc, I guess for every time you call
> execve(2), ld.so(8) will be run, and the tunables stored in ld.so.cache
> will be used.  Is this correct?

I think this rabbit hole is too deep for this part of the man page.  We
need a short sentence that's obvious to the reader, not a diatribe on
how the linux kernel works.

I'm happy with something like "The resulting data is read when the
program starts." regardless of how ambiguous or technically incorrect it
might be ;-)


  parent reply	other threads:[~2026-08-07  3:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 20:44 [PATCH v5 2/4] man/man5/tunables.conf: Document system-wide tunables config DJ Delorie
2026-08-06 22:02 ` Alejandro Colomar
2026-08-06 22:15   ` DJ Delorie
2026-08-07  0:06     ` Alejandro Colomar
2026-08-07  0:11       ` Alejandro Colomar
2026-08-07  0:15         ` Alejandro Colomar
2026-08-07  3:25       ` DJ Delorie [this message]
2026-08-07 22:36         ` Alejandro Colomar
2026-08-08  3:08           ` DJ Delorie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xntsp6393q.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.