Arnaldo,

Setting tx_qlen=0 did not help, the receiver receives only 1 packet, despite of 
sender's sending 10 packets. Attached are the dmesg output of sender & 
receiver. I modified the DCCP code on the sender side to print some debug 
messages (input/output to/from functions, etc.).

BTW, I am using CCID3.


----- Original Message ----
From: Arnaldo Carvalho de Melo <[EMAIL PROTECTED]>
To: Ian McDonald <[EMAIL PROTECTED]>
Cc: Leandro Melo de Sales <[EMAIL PROTECTED]>; burak gorkemli <[EMAIL 
PROTECTED]>; DCCP Mailing List <[email protected]>
Sent: Thursday, November 30, 2006 12:51:11 PM
Subject: Re:

On 11/29/06, Ian McDonald <[EMAIL PROTECTED]> wrote:
> Folks,
>
> Another thing to note is that with a limit on tx queue sizes now you
> will get EAGAIN if the queue is full...

Yes, 4, 5 packets should be, in dccp_sendmsg:

        if (sysctl_dccp_tx_qlen &&
            (sk->sk_write_queue.qlen >= sysctl_dccp_tx_qlen)) {
                rc = -EAGAIN;
                goto out_release;
        }

Leandro and Burak: could you please try setting sysctl_dccp_tx_qlen to
zero? doing this:

[EMAIL PROTECTED] ~]# cat /proc/sys/net/dccp/default/tx_qlen
5
[EMAIL PROTECTED] ~]# echo 0 > /proc/sys/net/dccp/default/tx_qlen
[EMAIL PROTECTED] ~]# cat /proc/sys/net/dccp/default/tx_qlen
0
[EMAIL PROTECTED] ~]#

And report the results?

- Arnaldo
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Attachment: receiver.dmesg
Description: Binary data

Attachment: sender.dmesg
Description: Binary data

Reply via email to