Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - 802.1Qbu frame preemption implementation #24

Closed
yue2388253 opened this issue Sep 15, 2021 · 5 comments
Closed

Question - 802.1Qbu frame preemption implementation #24

yue2388253 opened this issue Sep 15, 2021 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@yue2388253
Copy link

Hi,

I was wondering whether CoRE4INET support IEEE 802.1Qbu frame preemption?

Best
Lam

@Musteblume
Copy link
Member

Hi Lam

no preemption is not supported by the public CoRE4INET version.
We have some old implementation on a different branch, but this is not compatible with the newer contained Qbv shaper implementation.

Best regards
Philipp

@Musteblume Musteblume added the question This is a question label Sep 15, 2021
@Musteblume Musteblume self-assigned this Sep 15, 2021
@yue2388253
Copy link
Author

Hi Philipp,

Thank you for reply.
Are there any plans to implement this feature?
Another question is that whether a lookahead mechanism is enabled in switches. Lookahead mechanism means that in 802.1Qbv network, the switch will not transmit a frame if the remaining open time is too short to transmit the frame.

Best,
Lam

@Musteblume
Copy link
Member

Hi Lam,

currently there are no plans for preemption.
The next inet-framework version will include many TSN features in addition to preemption: https://www.youtube.com/watch?v=5kn7eQkvdUg

The lookahead mechanism is currently not implemented in the Qbv shaper.
You could extend IEEE8021QbvGate::isOpen() to look for the size of the next frame in the queue and compare it with the next timestamp in the Gate Control List.

Hope this helps
Best regards
Philipp

@Musteblume Musteblume added the enhancement New feature or request label Sep 17, 2021
@yue2388253
Copy link
Author

Hi Philipp,

Thank you for your reply!
I have tried to use INET 4.3.0 but it seems the TSN-related features are not fully implemented and it has limited examples about TSN, which make it difficult to use.
And I also tried NeSTing but it fails to run CQF since 802.1Qci is not implemented.
Will CoRE4INET continue to update TSN-related features? (For example, 802.1Qcr, parternoster queuing and so on)

Best,
Lam

@Musteblume
Copy link
Member

Hi Lam,

INET 4.4.x will include many TSN-related features with many examples and documentation. (Qcr is also included)

We actively use CoRE4INET for our research currently and in the future.
So, we implement features that we need for our research and publish all mature extensions.
Thats why i cannot say which features will be added in the future.
We are also happy to integrate pull requests with features implemented by others.

Hope this answers your question
Best regards
Philipp

@Musteblume Musteblume removed the question This is a question label Apr 23, 2022
@CoRE-RG CoRE-RG locked and limited conversation to collaborators Apr 23, 2022
@Musteblume Musteblume converted this issue into discussion #30 Apr 23, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants