OpenVehicleDiag
bumpalo
OpenVehicleDiag | bumpalo | |
---|---|---|
13 | 16 | |
741 | 1,298 | |
- | - | |
0.0 | 7.5 | |
over 1 year ago | 18 days ago | |
Rust | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OpenVehicleDiag
-
Rust in Automotive
BTW I have a few automotive projects if you wish to check them out! https://github.com/rnd-ash/ecu\_diagnostics https://github.com/rnd-ash/openvehiclediag https://github.com/rnd-ash/canviewer-rs
-
ECU_Diagnostics 0.90.0! - Nearing Version 1.0
Currently, there are no other tools other than my own that utilize this crate, but I hope that can soon change! * OpenVehicleDiag - A front-end for the ECU_Diagnostic crate, allowing for CAN manipulation and tracing, and KWP/OBD/UDS ECU diagnostics and custom payload sending
-
Mazda RX-8 reverse engineering notes!
The tool I am using to reverse engineer the car is my beta version of OpenVehicleDiag (Source code available here https://github.com/rnd-ash/openvehiclediag/tree/egui_ecu_diag).
-
New project for ISO 15765 .dbc file
Author of OpenVehicleDiag here. I already kinda had something like this in mind, so set up this JSON Schema my application uses: https://github.com/rnd-ash/OpenVehicleDiag/blob/main/SCHEMA.md
-
What's everyone working on this week (19/2021)?
Working on my vehicle/ECU diagnostics platform. https://github.com/rnd-ash/openvehiclediag/
- OpenVehicleDiag 1.0 now released - A powerful cross platform car diagnostics and ECU testing platform - Now supports SocketCAN as well as an experimental Linux port of the J2534 Passthru API for diagnostic adapters (Read OP for more info)
-
OpenVehicleDiag 1.0 and MacchinaJ2534! - A powerful Rust open source car diagnostic application and Passthru adapter driver!
Macchina-J2534: https://github.com/rnd-ash/Macchina-J2534 OpenVehicleDiag: https://github.com/rnd-ash/OpenVehicleDiag/
- OVD - Cross-platform Motor Vehicle ECU Diag Suite
-
OpenVehicleDiag milestone 2 - Extracting proprietary DTC error code descriptions from Daimler CBF files with Rust and converting to an open JSON schema with Serde (read OP)!
This is the next major milestone of OVD (https://github.com/rnd-ash/OpenVehicleDiag/), in which I have been able to write a binary file parser to extract ECU information from Daimler's CBF files in Rust. The parser can be found in the CBFParser directory of the main repository.
-
Converting Daimler CBF files to a more universal and open JSON standard! - And allowing my program (OpenVehicleDiag) to scan ECUs using the JSON
Source code: https://github.com/rnd-ash/OpenVehicleDiag/
bumpalo
-
Rust vs Zig Benchmarks
Long story short, heap allocation is painfully slow. Any sort of malloc will always be slower than a custom pool or a bump allocator, because it has a lot more context to deal with.
Rust makes it especially hard to use custom allocators, see bumpalo for example [0]. To be fair, progress is being made in this area [1].
Theoretically one can use a "handle table" as a replacement for pools, you can find relevant discussion at [2].
[0] https://github.com/fitzgen/bumpalo
-
Rust Memory Management
There are ways to accomplish this as well. Different allocator libraries exist for this kind of scenario, namely bumpallo which allocates a larger block of memory from the kernel, and allocates quickly thereafter. That would amortize the cost of memory allocations in the way I think you're after?
- Custom allocators in Rust
-
A C Programmers take on Rust.
Meaning, storing a lot of things in the same block of allocated memory? Vec is a thing, you know. There's also a bump allocator library.
-
Hypothetical scenario - What would be better - C, C++ or Rust? (Read desc.)
There are data structures like slotmap, and relatively low-level crates like bumpalo. This is not to say that either fits your use case, just that you definitely have access to the necessary parts to fit what you describe.
-
Implementing "Drop" manually to show progress
Sometimes you can put everything in a bump allocator, then when you're done, free the entire bump allocator in one go. https://docs.rs/bumpalo/
-
Any languages doing anything interesting with allocators?
This is useful with crates like bumpalo which give you bump-allocation arenas whose lifetimes are tied to the objects they allocate.
-
I’m Porting the TypeScript Type Checker Tsc to Go
TSC doesn't need to "stick around", right? Just a run-once and the program is over?
In those cases, https://github.com/fitzgen/bumpalo works amazingly as an arena. You can pretty much forget about reference counting and have direct references everywhere in your graph. The disadvantage is that it's hard to modify your tree without leaving memory around.
We use it extensively in http://github.com/dioxusLabs/dioxus and don't need to worry about Rc anywhere in the graph/diffing code.
-
Allocating many Boxes at once
Probably bumpalo, but then its Box will have a lifetime parameter - bumpalo::boxed::Box<'a, dyn MyTrait>
-
Graydon Hoare: What's next for language design? (2017)
Strictly speaking, Rust doesn't need this as a built-in language feature, because its design allows it to be implemented as a third-party library: https://docs.rs/bumpalo
The biggest problem is that there's some awkwardness around RAII; I'm not sure whether that could have been avoided with a different approach.
Of course, ideally you'd want it to be compatible with the standard-library APIs that allocate. This is implemented, but is not yet at the point where they're sure they won't want to make backwards-incompatible changes to it, so you can only use it on nightly. https://doc.rust-lang.org/stable/std/alloc/trait.Allocator.h...
Or are you suggesting that the choice of allocator should be dynamically scoped, so that allocations that occur while the bump allocator is alive automatically use it even if they're in code that doesn't know about it? I think it's not possible for that to be memory-safe; all allocations using the bump allocator need to know about its lifetime, so that they can be sure not to outlive it, which would cause use-after-free bugs. I'm assuming that Odin just makes the programmer responsible for this, and if they get it wrong then memory corruption might occur; for a memory-safe language like Rust, that's not acceptable.
What are some alternatives?
Macchina-J2534 - J2534 drivers for various Macchina hardware
rust-phf - Compile time static maps for Rust
ddt4all - OBD tool
generational-arena - A safe arena allocator that allows deletion without suffering from the ABA problem by using generational indices.
MacchinaM2-J2534-Rust - Cross platform J2534 API for Macchinas M2 UTD module
hashbrown - Rust port of Google's SwissTable hash map
grenad - Tools to sort, merge, write, and read immutable key-value pairs :tomato:
moonfire-nvr - Moonfire NVR, a security camera network video recorder
substrate-open-working-groups - The Susbstrate Open Working Groups (SOWG) are community-based mechanisms to develop standards, specifications, implementations, guidelines or general initiatives in regards to the Substrate framework. It could, but not restricted to, lead to new Polkadot Standards Proposals. SOWG is meant as a place to find and track ongoing efforts and enable everybody with similar interests to join and contribute.
feel
WDBXEditor - A communal program to edit all variants of Blizzard's client db files.