xsk | CMS and Web Server written in ShellScript

by o8vm Shell Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | xsk Summary

xsk is a Shell library typically used in Utilities applications. xsk has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

CMS and Web Server written in only ShellScript. It has RESTful interface and supports authentication mechanism using signature. This project supports rendering markdown and executing shell scripts.

Support

Quality

Security

License

Reuse

Support

xsk has a low active ecosystem.

It has 9 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

xsk has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of xsk is current.

Quality

xsk has 0 bugs and 0 code smells.

Security

xsk has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

xsk code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

xsk does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

xsk releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of xsk

Get all kandi verified functions for this library.

xsk Key Features

No Key Features are available at this moment for xsk.

xsk Examples and Code Snippets

No Code Snippets are available at this moment for xsk.

Community Discussions

Trending Discussions on xsk

reading updated value of ebpf's BPF_MAP_TYPE_HASH in userspace | Can read() linux function be used to get current value of object shared through map

AF-XDP: Implement Shared Umem sockets

AF_XDP: Set `SO_TIMESTAMP` not supported for `SO_XDP`: Protocol not available

AF-XDP: How do I get `ctx->data_meta` from kernel into user-space?

QUESTION

reading updated value of ebpf's BPF_MAP_TYPE_HASH in userspace | Can read() linux function be used to get current value of object shared through map

Asked 2022-Jan-16 at 12:10

So I have a kernel ebpf program that attach xdp hook to interface eno1, and in it I have a map ip_map that is of type BPF_MAP_TYPE_HASH that I am sharing with userspace. So in my userspace I am getting map's file descriptor, But now I like to get updated values of struct share_me which I am sharing with the help of BPF_MAP_TYPE_HASH type map in my userspace loader program.

Any anyone please help me explain a bit, as to how I can do this,

So I am assuming if my map_fd is pointing to BPF_MAP_TYPE_HASH is pointing to my MAP then I can just do this int sizeof_share_me_read=read(map_fd,&share_me,sizeof(struct share_me)); so this way I can read current updated value of my map_fd(BPF_MAP_TYPE_HASH) shared from kernel ebpf program and that will contain current packet's ip header in struct iphdr dest_ip member of share_me object. Can any one please help me sort this out

user.c

...

ANSWER

Answered 2022-Jan-16 at 12:10

Now that you have the map fd, you need to use libbpf's bpf_map_lookup_elem function to read the values:

Source https://stackoverflow.com/questions/70729426

QUESTION

AF-XDP: Implement Shared Umem sockets

Asked 2020-Mar-12 at 16:24

I want to implement XDP_SHARED_UMEM: https://www.kernel.org/doc/html/latest/networking/af_xdp.html#xdp-shared-umem-bind-flag

The libbpf library function xsk_socket__create (https://github.com/libbpf/libbpf/blob/master/src/xsk.c) checks the xsk_umem->refcount value. In case it is greater than 1, the XDP_SHARED_UMEM option of a struct sockaddr_xdp is set.

So as far as I understand correctly, I "just" need to pass the original umem struct of the socket I want to share the umem with and the rest is done by libbpf.

The way I tried to do it was to let the first process copy its umem-struct into a shared-memory area where the second process could load it from. But because struct xsk_umem is defined in xsk.c it is hidden from the user and I am not able to do something like this:

memcpy(shdm_ptr, umem, sizeof(struct xsk_umem))

I don't know how they expect someone to use the shared umem feature?

...

ANSWER

Answered 2020-Mar-12 at 16:24

So this was discussed on the xdp-newbies mailing list. Reporting here for the record.

It is not recommended to go with a multi-process setup as you are trying to do. Björn says:

Note that if you'd like to do a multi-process setup with shared umem, you: need to have a control process that manages the fill/completion rings, and synchronize between the processes, OR re-mmap the fill/completetion ring from the socket owning the umem in multiple processes and synchronize the access to them. Neither is pleasant.

Honestly, not a setup I'd recommend.

And he adds:

Just for completeness; To setup shared umem:

create socket 0 and register the umem to this.

mmap the fr/cr using socket 0

create socket 1, 2, n and refer to socket 0 for the umem.

So, in a multiprocess solution step 3 would be done in separate processes, and step 2 depending on your application. You'd need to pass socket 0 to the other processes and share the umem memory from the process where socket 0 was created. This is pretty much a threaded solution, given all the shared state.

I advice not taking this path.

(Credits to Björn.)

Source https://stackoverflow.com/questions/60615240

QUESTION

AF_XDP: Set `SO_TIMESTAMP` not supported for `SO_XDP`: Protocol not available

Asked 2020-Mar-09 at 09:03

Why is setting SO_TIMESTAMP not supported for an AF_XDP socket? The user manual of my driver (mlnx 5.0) states that

Incoming packets are time-stamped before they are distributed on the PCI depending on the congestion in the PCI buffers.

To my knowledge, before distributed on the PCI means that there is no Linux Kernel involved (yet) - right?

I tried setting it like this:

...

ANSWER

Answered 2020-Mar-09 at 09:03

There is no technical reason on why it is not implemented.

Indeed, it looks like it is on the To-Do list of the xdp development team.

Cite from here:

Important medium-term tasks
...
Metadata from hardware
There are various hardware metadata items that would be useful for XDP programs to access, to reduce the amount of processing that needs to happen in eBPF. These include:

Checksum

Hash value

Flow designator

Higher-level protocol header offsets

Timestamps

It looks like this is on the To-Do since June 2019, so it probably doesn't have top priority, otherwise it would already be implemented.

Source https://stackoverflow.com/questions/60596764

QUESTION

AF-XDP: How do I get `ctx->data_meta` from kernel into user-space?

Asked 2020-Mar-03 at 11:09

I want to measure packet latency for my AF-XDP program. I was looking at this reference: https://github.com/xdp-project/xdp-project/blob/master/areas/arm64/xdp_for_tsn.org

and adapted it to this:

...

ANSWER

Answered 2020-Mar-03 at 11:09

The snippet you used is described in the tutorial as pseudo-code, it is not a complete and functional example. Let's have a look at the verifier log:

Source https://stackoverflow.com/questions/60487925

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install xsk

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: