Basically I'm replacing net package partially rn with custom DPDK-enabled impl right now i.e. everything syscall.Socket related. It's not about the protocols, it's about replacing whole BSD sock API and epoll/kqueue with a custom impl enterily. I've managed to impl a PoC for this, might create a golang PR soon(-ish) after getting some opinions. Dubbed at slack #dartarts. On Monday, July 20, 2020 at 9:38:26 PM UTC+3 Ian Lance Taylor wrote:
> On Mon, Jul 20, 2020 at 7:53 AM Yuriy Yarosh <void....@gmail.com> wrote: > > > > Basically I've got some different tcp/ip stack implementations based on > DPDK and want to be able to replace existing types and methods of the stock > net package, which would allow to add DPDK support for existing apps > without any amends as a complete plug'n'play. > > Same goes for JSON serialization and similar non-optimized > implementations. > > > > Stdlib shouldn't be perfect, but developers should be able to use > optimized implementations as a drop-in replacement when necessary. > > > > What do you think guys ? > > I'm not sure quite what you are suggesting. But the net package does > intend to support alternate protocols via calls like syscall.Socket > followed by os.NewFile and net.FileConn. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/c37ffcc3-d787-446d-9812-bdfc25a3ac8en%40googlegroups.com.
