netdev - Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 21 Jan 2009 14:50:15 +0100 (CET)
From:	kristrev@...ula.no
To:	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>
Cc:	kristrev@...ula.no, "Andreas Petlund" <apetlund@...ula.no>,
	"Netdev" <netdev@...r.kernel.org>, griff@...ula.no,
	paalh@....uio.no
Subject: Re: RFC: Latency reducing TCP modifications for thin-stream      
     interactive applications

Hello,

> Trimmed all but netdev (and .no addresses) from cc list.

Thank you.

>> If I have understood the code correctly, what will then be the
>> difference
>> between our current solution and the one you suggest (except we can
>> remove
>> one of the bundling methods and when a packet is retransmitted)? If I
>> have
>> not understood the code correctly, feel free to yell :) (if it is a
>> misunderstanding, it also explains all the checks for skb->cloned).
>
> It didn't mean clone an skb but copy the relevant data into new skb which
> is then not put into write queue at all but given to lower layers only.

Thank you, now I understand what you meant and I agree that it is a better
solution. However, when I think of it, copying might be too resource
intensive and thus remove all gains from RDB. We have seen streams with 
small packets and very low interarrival times, which would lead to a large
number of copy-operations every second. I will implement it and compare
performance.

-Kristian

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