From: Jonathan Corbet <corbet@lwn.net>
To: Otto Sabart <ottosabart@seberm.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/3] doc: networking: prepare scaling document for conversion into RST
Date: Wed, 16 Jan 2019 15:03:07 -0700 [thread overview]
Message-ID: <20190116150307.67eb2201@lwn.net> (raw)
In-Reply-To: <9a37aecf3f7e5b0df579f4c72885b0716f5abd6c.1547063330.git.ottosabart@seberm.com>
On Wed, 9 Jan 2019 20:57:22 +0100
Otto Sabart <ottosabart@seberm.com> wrote:
> Add markups which are necessary for successful conversion into
> reStructuredText.
>
> There are no semantic changes.
>
> Signed-off-by: Otto Sabart <ottosabart@seberm.com>
This seems generally good, except:
> Documentation/networking/scaling.txt | 131 +++++++++++++++++----------
> 1 file changed, 85 insertions(+), 46 deletions(-)
>
> diff --git a/Documentation/networking/scaling.txt b/Documentation/networking/scaling.txt
> index b7056a8a0540..0ce13ed103bd 100644
> --- a/Documentation/networking/scaling.txt
> +++ b/Documentation/networking/scaling.txt
> @@ -1,4 +1,8 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +=====================================
> Scaling in the Linux Networking Stack
> +=====================================
>
>
> Introduction
> @@ -10,11 +14,11 @@ multi-processor systems.
>
> The following technologies are described:
>
> - RSS: Receive Side Scaling
> - RPS: Receive Packet Steering
> - RFS: Receive Flow Steering
> - Accelerated Receive Flow Steering
> - XPS: Transmit Packet Steering
> +- RSS: Receive Side Scaling
> +- RPS: Receive Packet Steering
> +- RFS: Receive Flow Steering
> +- Accelerated Receive Flow Steering
> +- XPS: Transmit Packet Steering
>
>
> RSS: Receive Side Scaling
> @@ -45,7 +49,9 @@ programmable filters. For example, webserver bound TCP port 80 packets
> can be directed to their own receive queue. Such “n-tuple” filters can
> be configured from ethtool (--config-ntuple).
>
> -==== RSS Configuration
> +
> +RSS Configuration
> +`````````````````
The use of the heading levels is kind of strange; I'm not really sure why
you did it that way? I'd rather this adhered to our normal hierarchy, so
it should be:
RSS Configuration
-----------------
All of the other bottom-level headings should be as well.
Fix that up, please, and I can take these. The whole series can also be
squashed into a single patch (though I don't feel really strongly about
that either way).
Thanks,
jon
next prev parent reply other threads:[~2019-01-16 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 19:57 [PATCH 0/3] doc: networking: integrate scaling document into doc tree Otto Sabart
2019-01-09 19:57 ` [PATCH 1/3] doc: networking: prepare scaling document for conversion into RST Otto Sabart
2019-01-16 22:03 ` Jonathan Corbet [this message]
2019-01-09 19:57 ` [PATCH 2/3] doc: networking: convert scaling doc " Otto Sabart
2019-01-09 19:57 ` [PATCH 3/3] doc: networking: add scaling doc into index file Otto Sabart
2019-01-16 4:35 ` [PATCH 0/3] doc: networking: integrate scaling document into doc tree David Miller
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=20190116150307.67eb2201@lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ottosabart@seberm.com \
/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.