From: kristrev@simula.no
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: kristrev@simula.no, "Andreas Petlund" <apetlund@simula.no>,
"Netdev" <netdev@vger.kernel.org>,
griff@simula.no, paalh@ifi.uio.no
Subject: Re: RFC: Latency reducing TCP modifications for thin-stream interactive applications
Date: Wed, 21 Jan 2009 14:50:15 +0100 (CET) [thread overview]
Message-ID: <92d5db086b180f1241f7258fabae8f1b.squirrel@webmail.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.64.0901201736370.1889@wrl-59.cs.helsinki.fi>
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
next prev parent reply other threads:[~2009-01-21 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 14:54 RFC: Latency reducing TCP modifications for thin-stream interactive applications Andreas Petlund
2009-01-14 15:32 ` Ilpo Järvinen
2009-01-16 10:13 ` kristrev
2009-01-20 15:45 ` Ilpo Järvinen
2009-01-21 13:50 ` kristrev [this message]
2009-01-22 14:13 ` Ilpo Järvinen
[not found] <492EA31D.8000704@simula.no>
2008-11-28 12:25 ` Ilpo Järvinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92d5db086b180f1241f7258fabae8f1b.squirrel@webmail.uio.no \
--to=kristrev@simula.no \
--cc=apetlund@simula.no \
--cc=griff@simula.no \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=paalh@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).