From: Guillaume Nault <gnault@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] rtnetlink.7: Document metrics attributes (RTAX_*).
Date: Wed, 8 Oct 2025 20:51:24 +0200 [thread overview]
Message-ID: <aOayrL0umGBiQpsZ@debian> (raw)
In-Reply-To: <z45wvnlrxlnrp367rgxotuieieyn7myfgct6lvjitn4igupo74@htps4hpfqamb>
On Wed, Oct 08, 2025 at 06:05:41PM +0200, Alejandro Colomar wrote:
> Hi Guillaume,
>
> On Wed, Oct 08, 2025 at 04:41:19PM +0200, Guillaume Nault wrote:
> > > > +.IP
> > > > +.in +4n
> > >
> > > I would use
> > >
> > > .RS
> > > .IP
> > >
> > > and get rid of the .in +4n.
> >
> > I have no preference, I was just following the commands used elsewhere
> > in this man page.
>
> Hmmm, I'll have a look at the source of that page later. Maybe I need
> to fix the existing code.
>
> > > > +.TE
> > >
> > > And here use .RE.
> >
> > Okay, I'll use .RS/.RE in v2.
> >
> > > > +.IP
> > > > +Metrics that are locked with
> > > > +.B RTAX_LOCK
> > > > +take precedence over the values normally used by the kernel
> > > > +(computed or assigned by a sysctl or setsockopt(2)).
> > > > +Therefore, some metrics, like
> > > > +.BR RTAX_RTO_MIN ,
> > > > +have no effect unless their bit is set in
> > > > +.BR RTAX_LOCK .
> > > > +.in
> > >
> > > I find this placement of .in weird. The preceding paragraph isn't
> > > indented by it. I think I prefer using .RS/.RE, and then you'd have to
> > > put .RE before this paragraph to get the same indentation.
> > >
> > > Here's how your patch looks like:
> > >
> > > $ MANWIDTH=72 diffman-git HEAD 2>/dev/null
> > > --- HEAD^:man/man7/rtnetlink.7
> > > +++ HEAD:man/man7/rtnetlink.7
> > > @@ -218,7 +218,8 @@ DESCRIPTION
> > > RTA_GATEWAY protocol address The gateway of the route
> > > RTA_PRIORITY int Priority of route
> > > RTA_PREFSRC protocol address Preferred source address
>
> [...]
>
> > > + RTAX_RTO_MIN __u32 Minimum Retransmission TimeOut to use for this route
> > > + RTAX_INITRWND __u32 Initial size of the receive window for this route
> > > + RTAX_QUICKACK __u32 Use quick ack for this route
> > > + RTAX_CC_ALGO asciiz string Congestion Control algorithm to use for this route
> > > + RTAX_FASTOPEN_NO_COOKIE __u32 Allow TCP Fast Open without cookie
> > > +
> > > + Metrics that are locked with RTAX_LOCK take precedence over
> > > + the values normally used by the kernel (computed or as‐
> > > + signed by a sysctl or setsockopt(2)). Therefore, some met‐
> > > + rics, like RTAX_RTO_MIN, have no effect unless their bit is
> > > + set in RTAX_LOCK.
> > > +
> > > RTA_MULTIPATH contains several packed instances of struct
> > > rtnexthop together with nested RTAs (RTA_GATEWAY):
> > >
> > > Is this indentation what you intended?
> >
> > Yes.
>
> Thanks!
>
> > Is that indentation confusing? I can change it if necessary.
>
> The indentation is fine. Please keep it like that. What's confusing is
> the source code, since the '.in' goes after the unindented paragraph,
> while I'd expect it to be the indentation terminator. .RS/.RE is much
> more intuitive.
I understand what you mean now. Placing '.in' after the RTAX_LOCK
paragraph was an oversight.
I'm about to send v2, with .in replaced by .RS/.RE, as you proposed.
Thanks for the feedbacks!
>
> Have a lovely day!
> Alex
>
> --
> <https://www.alejandro-colomar.es>
> Use port 80 (that is, <...:80/>).
next prev parent reply other threads:[~2025-10-08 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 10:53 [PATCH] rtnetlink.7: Document metrics attributes (RTAX_*) Guillaume Nault
2025-10-02 14:43 ` Guillaume Nault
2025-10-02 14:59 ` Alejandro Colomar
2025-10-02 15:06 ` Guillaume Nault
2025-10-02 21:33 ` Alejandro Colomar
2025-10-08 14:41 ` Guillaume Nault
2025-10-08 16:05 ` Alejandro Colomar
2025-10-08 18:51 ` Guillaume Nault [this message]
2025-10-12 21:28 ` Alejandro Colomar
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=aOayrL0umGBiQpsZ@debian \
--to=gnault@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.