netdev - Re: Adding support for ARINC429 into the Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130701100624.GB19798@amd.pavel.ucw.cz>
Date:	Mon, 1 Jul 2013 12:06:24 +0200
From:	Pavel Machek <pavel@....cz>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: Adding support for ARINC429 into the Linux kernel

Hi!

> > My vote would be for a new socket family for the low-level protocol,
> > with room for extension later to support the advanced features.
> > 
> > This should be one of the simplest socket implementations possible, if
> > you just need to send and receive 32 bit words, and can bind to a
> > a set of labels for rx as you described above.
> > 
> > The only possible concern I see with that interface is slightly higher
> > latency than what you would be able to get with a straight read/write
> > based character device.
> > 
> Any further feedback on this ?
> 
> Key question: Would a new address family have a chance of being accepted ?

Yes... that seems like cleanest way to implement it.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html