* Re: ss: Checking efficient analysis for network connections
2019-06-01 23:48 ` David Miller
@ 2019-06-02 5:40 ` Markus Elfring
2019-06-13 14:40 ` Markus Elfring
` (3 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Markus Elfring @ 2019-06-02 5:40 UTC (permalink / raw)
To: David Miller, David Ahern, Stephen Hemminger
Cc: Josh Hunt, netdev, linux-kernel
> If you use netlink operations directly,
Thanks for such feedback.
Should this programming interface become better known?
> you can have the kernel filter on various criteria
> and only get the socket entries you are interested in.
This is good to know.
> This whole discussion has zero to do with what text format 'ss' outputs.
Some software components are affected here.
The socket statistic tool is using data from the directory “/proc/net”.
* Provided text files refer to known Linux data formats.
Can it happen to work with other data formats there?
* The analysis program can also be extended for the support
of additional data formats, can't it?
Regards,
Markus
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ss: Checking efficient analysis for network connections
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
` (2 subsequent siblings)
4 siblings, 0 replies; 8+ messages in thread
From: Markus Elfring @ 2019-06-13 14:40 UTC (permalink / raw)
To: David Miller, David Ahern, Stephen Hemminger
Cc: Josh Hunt, netdev, linux-kernel
> This whole discussion has zero to do with what text format 'ss' outputs.
Would you like to support the clarification of additional data formats
for the usage of specific information by tools for socket statistics
(from the directory “/proc/net” and related ones)?
Regards,
Markus
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ss: Checking efficient analysis for network connections
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-10-22 6:00 ` [RFC] " Markus Elfring
4 siblings, 0 replies; 8+ messages in thread
From: Markus Elfring @ 2019-07-23 8:25 UTC (permalink / raw)
To: David Miller, David Ahern, Stephen Hemminger, netdev
Cc: Josh Hunt, linux-kernel
> This whole discussion has zero to do with what text format 'ss' outputs.
Do any more software developers care for the clarification of
additional data formats for the usage of specific information by tools
around socket statistics (from the directory “/proc/net” and related ones)?
Would you like to achieve any improvements in this area?
Regards,
Markus
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: ss: Checking selected network ports
2019-06-01 23:48 ` David Miller
` (2 preceding siblings ...)
2019-07-23 8:25 ` Markus Elfring
@ 2019-09-16 10:32 ` Markus Elfring
2019-10-22 6:00 ` [RFC] " Markus Elfring
4 siblings, 0 replies; 8+ messages in thread
From: Markus Elfring @ 2019-09-16 10:32 UTC (permalink / raw)
To: David Miller, David Ahern, Stephen Hemminger, netdev
Cc: Josh Hunt, linux-kernel, kernel-janitors
> 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.
I suggest to take another look at 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [RFC] ss: Checking selected network ports
2019-06-01 23:48 ` David Miller
` (3 preceding siblings ...)
2019-09-16 10:32 ` ss: Checking selected network ports Markus Elfring
@ 2019-10-22 6:00 ` Markus Elfring
4 siblings, 0 replies; 8+ messages in thread
From: Markus Elfring @ 2019-10-22 6:00 UTC (permalink / raw)
To: netdev, kernel-janitors, linux-doc
Cc: linux-kernel, David Ahern, David Miller, Josh Hunt, Stephen Hemminger
> 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
^ permalink raw reply [flat|nested] 8+ messages in thread