-
Notifications
You must be signed in to change notification settings - Fork 196
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
added quic support to fddev bench. Numerous QUIC fixes. #1655
Conversation
ulong no_stream; | ||
|
||
// vector receive members | ||
struct mmsghdr rx_msgs[IO_VEC_CNT]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move all this QUIC stuff out to another file or like, fd_quic_client_t
? I feel like there could be a simple minimal interface which the bench tile can call without needing all of this stuff in its namespace.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we do this in a follow up PR. fd_quic_test_client_t
or something.
uchar signature[ static 64 ], | ||
uchar const payload[ static 130 ] ) { | ||
fd_tls_test_sign_ctx_t * ctx = (fd_tls_test_sign_ctx_t *)_ctx; | ||
fd_ed25519_sign( signature, payload, 130UL, ctx->public_key, ctx->private_key, ctx->sha512 ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about signing on the benchs. The design here is that benchg is scalable and does signing, and benchs just sends on the socket (which is very expensive). If you are mixing those two things it makes the scaling story for the bench topology much more complicated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you think doing it in bencho is a better choice?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you know, this signing only occurs during handshaking
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, hmm. Then after that it's just TLS or whatever?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmcgee-jump This signer interface is used by the TLS library to prove that it's in possession of the identity key. It only happens once per QUIC connection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I think we should add unit tests that exercise all the messed up ACK handling rules in the QUIC protocol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Introduces a remote DoS bug
7fdf79c
to
e13af38
Compare
bench code needs the following, but putting these into another PR:
quic_enable - hard coded flag to use quic rather than udp: should be configurable
only supports one connection. Each benchs should have a connection for each fd_quic tile
This PR should help us move forward with the demo