moby/vendor/github.com/Microsoft/go-winio
Kevin Parsons e1f0f77bf4 Revendor go-winio
This is needed to provide fixes for ETW on ARM. The updated ETW package will
no-op on ARM, rather than crashing. Further changes are needed to Go itself to
allow ETW on ARM to work properly.

Signed-off-by: Kevin Parsons <kevpar@microsoft.com>
2019-04-22 14:23:53 -07:00
..
archive/tar project: use vndr for vendoring 2016-11-03 15:31:46 -07:00
backuptar Revendor hcsshim and go-winio 2018-08-23 12:03:33 -07:00
pkg Revendor go-winio 2019-04-22 14:23:53 -07:00
vhd Vendor Microsoft/go-winio@4de24ed3 2019-03-12 18:41:46 -07:00
backup.go Revendor Microsoft/go-winio @ v0.4.5 2017-08-09 08:31:43 -07:00
ea.go Vendor Microsoft/go-winio v0.4.11 2018-09-06 09:54:24 -07:00
file.go Revendor go-winio 2019-04-22 14:23:53 -07:00
fileinfo.go Revendor hcsshim and go-winio 2018-08-23 12:03:33 -07:00
hvsock.go Revendor go-winio 2019-04-22 14:23:53 -07:00
LICENSE project: use vndr for vendoring 2016-11-03 15:31:46 -07:00
pipe.go Revendor go-winio 2019-04-22 14:23:53 -07:00
privilege.go Revendor go-winio to v0.3.7 2016-11-22 10:39:42 -08:00
README.md rerun vndr 2017-03-08 02:29:34 +00:00
reparse.go project: use vndr for vendoring 2016-11-03 15:31:46 -07:00
sd.go Revendor go-winio to v0.3.7 2016-11-22 10:39:42 -08:00
syscall.go Revendor go-winio 2019-04-22 14:23:53 -07:00
zsyscall_windows.go Revendor go-winio 2019-04-22 14:23:53 -07:00

go-winio

This repository contains utilities for efficiently performing Win32 IO operations in Go. Currently, this is focused on accessing named pipes and other file handles, and for using named pipes as a net transport.

This code relies on IO completion ports to avoid blocking IO on system threads, allowing Go to reuse the thread to schedule another goroutine. This limits support to Windows Vista and newer operating systems. This is similar to the implementation of network sockets in Go's net package.

Please see the LICENSE file for licensing information.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Thanks to natefinch for the inspiration for this library. See https://github.com/natefinch/npipe for another named pipe implementation.