Passive receive adrian #2
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
April 15, 2014 20:24
…rsions of stable/10 and head, but not on what I'm running. dwarf-4 doesn't get recognised by some of the base tools.
It's incomplete and totally barnjacked. But right now I just want to verify that the thread is created and the socket is correctly created.
…like curthread fail. * modify the IO loop to keep reading as required. It's goto hell and thus it must be rewritten.
* comments.
* start fleshing out what the multiple request type thing will look like.
I just realised how much I don't want to be hand-crafting this crap and libnv should do it for me. Let's try it out.
This again only supports the string type for now.
…e for it. Implement uinet_sysctl().
It's terrible - I'm just passing the oid data in as a binary blob. Any semblence of being endian-agnostic just went out the window.
* If we get no response buffer but we do have the length then set it to that. The "how big is X?" API involves doing a query for an OID, with no old buffer but with an oldlenp set. The size of the response is then put in oldlenp.
the resulting length.
modified by sysctl*() calls. I need to refactor out the common code between the str and oid paths, this is ridiculous.
…ssive_receive_adrian
added 7 commits
September 3, 2014 09:01
Thanks Valgrind!
* Zero-out the buffer being passed to it - it uses the contents of buf to stir its local entropy pool before it returns something, and that's causing valgrind to trip up on uninitialised data.
…om:/freenas-build/libuinet into passive_receive_adrian
…om:/freenas-build/libuinet into passive_receive_adrian
Otherwise builds dirty this file and cause much sadness.
This allows for users of uinet_if_bridge to know what the origin interface set was - internal or external interfaces. * interfaces passed to uinet_if_bridge already have directionality tagged. * change uinet_if_bridge to store the bif in the physical interface if_bridge parameter, rather than the bridge softc. * This allows the input path to check the directionality of the interface. * Whilst here, don't forward packets to interfaces that are the same directionality of the interface. * Tag the bridge packet with an mbuf flag indicating the directionality. * Percolate that through to l2info * .. and into libuinet_api.
…om:/freenas-build/libuinet into passive_receive_adrian
…drian Conflicts: Makefile bin/echo/Makefile
Clear flags before we use it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a bunch of stuff to implement a really dirty sysctl accessor API.