Separate NetStat parsing logic

[Dentrax]

As procfs already did use parseX(io.Reader) functions for other filesystem formats, this was missing in netstat parsing. It should not do both reading and parsing stuff in the same function. Anyone who want to just access parser func using go:linkname directive, now it's possible. I had to copy-paste the actual parser logic since the function itself also reads a file.

Signed-off-by: Furkan furkan.turkal@trendyol.com

[discordianfish]

Makes sense in general but neither functions are exposed, so they can't be used by consumers of the package anyway. We might want to consider exposing them. Do you have a use case for this?
But otherwise just for consistency alone this makes sense, so LGTM

[Dentrax]

so they can't be used by consumers of the package anyway

AFAIK, procfs doesn't expose parsing functions to the public in general. So this statement also valid for all other functions.

We might want to consider exposing them.

It would be nice to expose all parsing functions to public in another PR! You're right! I intentionally make this private for consistency.

Do you have a use case for this?

I am able to use other parse functions using go:linkname directive, but couldn't use this one. So have to copy+paste the actual logic. I'm not working on Linux, but I have a netstat file that needed to parse.

Thanks! 🤗

[SuperQ]

Yes, let's make the parsing functions public. That would be very nice.