netdev - Re: TCP communication for raw image transmission

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 02 Jan 2012 17:29:05 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jean-Michel Hautbois <jhautbois@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: TCP communication for raw image transmission

Le lundi 02 janvier 2012 à 17:08 +0100, Jean-Michel Hautbois a écrit :

> Yes, and again, I don't want any missing lines :).
> 

Go for tcp :)


> I don't really know what it can do, but it has to do encoding (even if
> it is a SoC, with dedicated devices, memory has to be used).
> The main problem I have, is that I don't have the two boards with me
> today, and even if I can prototype on x86, I can't conclude as far as
> I don't test on the real HW.

Thats going to be tough. You could at least use one board and test if it
can send 100Mbits using netperf (on a x86 target), and check cpu usage.

> This is also why I want to prototype my best bet in the first try :).
> And this is mainly a networking/memory problem.

If the 'no packet loss happens in the network' requirement is OK, then a
plain sendfile() [ or splice() ] will work.

Limiting each tcp frame to a 1 or 2 lines of your image is about
limiting MSS on your tcp session (setsockopt( ... TCP_MAXSEG ))



--
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