Netutils-linux

Latest version: v2.7.11

Safety actively analyzes 613734 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

4.5

2.7.9

RSS

`rss-ladder` tool supports PCI-slot-based queue naming now. I mean this:


30: 127355089 0 0 0 PCI-MSI-edge mlx5_comp0pci:0000:01:00.0
31: 120112828 5482507 0 0 PCI-MSI-edge mlx5_comp1pci:0000:01:00.0
32: 121978940 0 5524729 0 PCI-MSI-edge mlx5_comp2pci:0000:01:00.0
33: 122736116 0 0 5465612 PCI-MSI-edge mlx5_comp3pci:0000:01:00.0


How to tune it?


$ rss-ladder pci:0000:01:00.0
- distribute interrupts of pci:0000:01:00.0 (mlx5_async_eq) on socket 0
- distribute interrupts of pci:0000:01:00.0 (mlx5_cmd_eq) on socket 0
- distribute interrupts of pci:0000:01:00.0 (mlx5_comp) on socket 0
- pci:0000:01:00.0: queue mlx5_comp0pci:0000:01:00.0 (irq 30) bound to CPU0
- pci:0000:01:00.0: queue mlx5_comp1pci:0000:01:00.0 (irq 31) bound to CPU1
- pci:0000:01:00.0: queue mlx5_comp2pci:0000:01:00.0 (irq 32) bound to CPU2
- pci:0000:01:00.0: queue mlx5_comp3pci:0000:01:00.0 (irq 33) bound to CPU3
- distribute interrupts of pci:0000:01:00.0 (mlx5_pages_eq) on socket 0


It may be not perfect but it works at least. Well, at least for mlx5 driver.

RPS

`autorps` tool doesn't yelling at you with dreadful exception if you try to tune multiqueue NIC. Just says that it may be wrong idea and you should use `-f` flag to really change RPS settings.

Also some processors have inverted CPU masks in `rps_cpus` file and you could put all processing on foreign NUMA node. I don't know how these masks work and don't want to know, so default behaviour now is to copy mask from `/sys/class/net/$dev/device/local_cpus` instead of evaluate it.

2.7.5

New class structure

There is a new class-structure in `server-info` utility and `netutils_linux_hardware` package:

Server class manages five subsystems - CPU, Disk, Net, Memory and System.

Server (server-info) can collect (--collect), read (--show) and rate (--rate) data.

Before the refactoring there were 3 big classes: Reader, Parser (--show) and Assessor (--rate). They had duplicated data about subsystems. Well, there were no "subsystems", there were just a lot of functions with prefixes in those classes. Now all those functions live in their own subsystems, all subsystems have standardised API (that's very cool for Server class, it can just iterate over subsystems).

Folding

There is a new `Folding` class with all the folding logic/constants. Also there is no more -f, -ff, -fff args, use --device, --subsystem, --server instead.

Other things

Some code was simplified and I restored run tests for `server-info --rate`. Also I got rid of `six.iteritems` dependency in few places and just use .items(). There no big data, so I don't think that 2-3 kbits of RAM are more than code simplicity.

2.7.4

All new options available:

shell
--cpu Show information about CPU
--memory Show information about RAM
--net Show information about network devices
--disk Show information about disks
--system Show information about system overall (rate only)


Example:
yaml
server-info --rate --device --net --cpu
cpu:
BogoMIPS: 5
CPU MHz: 5
CPU(s): 5
Core(s) per socket: 10
L3 cache: 7
Socket(s): 10
Thread(s) per core: 10
Vendor ID: 10
net:
eth1: 3.6666666666666665
eth6: 9.666666666666666
eth7: 9.666666666666666


It also works with `--show`:

yaml
server-info --show --memory --disk
disk:
vda:
model: null
size: 21474836480
type: HDD
memory:
devices:
'0x1100':
size: '512'
speed: 0
type: RAM
size:
MemFree: 78272
MemTotal: 500196
SwapFree: 0
SwapTotal: 0


Also if you run server-info without necessary parameters it shows more human-oriented error and --help output instead of traceback with AssertionError.

2.7.2

Well, I failed the challenge to release it before new 2018 year. But later is better than never!

Detail are boring, you'd better look at [examples in README](https://github.com/strizhechenko/netutils-linuxhardware-and-its-configuration-rating-server-info)!

1. All the server-info-* utils have one entry point now.
2. Old `server-info-rate` and `server-info-show` utils deleted.
3. `server-info-collect` called via wrapper until it will be rewritten in python. It's a separate issue.
4. Added (and fixed) tests for server-info --rate feature. It doesn't fail on all examples in `./tests/server-info-show.test/`
5. Yes, utils call looks like this now: `server-info --rate` instead of `server-info-rate`
6. You can collect data and optional pack it into tarball with `server-info --directory <path-to-directory> --gzip`. It will make `<path-to-directory>.tar.gz` with all the data that you can take from server for later analyze.
7. New examples are already in README.

2.7.1

You can now skip details of your server's rating this way:

Usage

- `server-info-rate -f` - shows entire device rate
- `server-info-rate -ff` - shows entire subsystem's rate
- `server-info-rate -fff` - shows entire server's rate

Example

shell
$ server-info-rate -fff
WARNING: why do you use 20 years old hardware, dude?


Just a joke. For example:

yaml
➜ vscale-vm git:(folding) ✗ server-info-rate -ff

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.