All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	David Miller <davem@davemloft.net>, Josh Hunt <johunt@akamai.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [RFC] ss: Checking selected network ports
Date: Tue, 22 Oct 2019 08:00:49 +0200	[thread overview]
Message-ID: <93483314-22eb-0ed6-70b3-044e6e007a34@web.de> (raw)
In-Reply-To: <20190601.164838.1496580524715275443.davem@davemloft.net>

> If you use netlink operations directly, you can have the kernel filter
> on various criteria and only get the socket entries you are interested in.

Do any developers care to take another look at current software design options?


> This whole discussion has zero to do with what text format 'ss' outputs.

Is there a need to improve the software documentation any further?

Which programming interface should be used to check the receive queue
for a single port (without retrieving more network data before)?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	David Miller <davem@davemloft.net>, Josh Hunt <johunt@akamai.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [RFC] ss: Checking selected network ports
Date: Tue, 22 Oct 2019 06:00:49 +0000	[thread overview]
Message-ID: <93483314-22eb-0ed6-70b3-044e6e007a34@web.de> (raw)
In-Reply-To: <20190601.164838.1496580524715275443.davem@davemloft.net>

> If you use netlink operations directly, you can have the kernel filter
> on various criteria and only get the socket entries you are interested in.

Do any developers care to take another look at current software design options?


> This whole discussion has zero to do with what text format 'ss' outputs.

Is there a need to improve the software documentation any further?

Which programming interface should be used to check the receive queue
for a single port (without retrieving more network data before)?

Regards,
Markus

  parent reply	other threads:[~2019-10-22  6:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  1:38 [PATCH v2] ss: add option to print socket information on one line Josh Hunt
2019-05-02 23:11 ` David Ahern
2019-05-30  9:11 ` Markus Elfring
2019-06-01  8:36 ` ss: Checking efficient analysis for network connections Markus Elfring
2019-06-01 23:48   ` David Miller
2019-06-02  5:40     ` Markus Elfring
2019-06-13 14:40     ` Markus Elfring
2019-07-23  8:25     ` Markus Elfring
2019-09-16 10:32     ` ss: Checking selected network ports Markus Elfring
2019-09-16 10:32       ` Markus Elfring
2019-10-22  6:00     ` Markus Elfring [this message]
2019-10-22  6:00       ` [RFC] " Markus Elfring

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=93483314-22eb-0ed6-70b3-044e6e007a34@web.de \
    --to=markus.elfring@web.de \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=johunt@akamai.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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.