From: Jamal Hadi Salim <jhs@mojatatu.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Send fail notifications
Date: Wed, 18 Dec 2013 14:06:12 +0000 [thread overview]
Message-ID: <52B1ABD4.1060108@mojatatu.com> (raw)
In-Reply-To: <52B1AA25.3000700@mojatatu.com>
A little more info:
- When i have MTU > 16K, no problem, 1 notification makes it through
with an EOR and proper info
EOR.
- ssf_flags are always zero (thats one other place that may have carried
such extra info)
- kernel 3.12.0 (with other non-sctp patches)
cheers,
jamal
On 12/18/13 08:59, Jamal Hadi Salim wrote:
>
> Lets say between server and client i have an MTU of 4K.
> I send 16K with partial reliability setting.
> If the data gets through the receiver sees (I think
> SCTP_PARTIAL_DELIVERY_POINT may change this behavior but it probably
> defaults to MTU):
>
> Msg1, 4k, !EOR
> Msg2, 4k, !EOR
> Msg3, 4k, !EOR
> Msg4, 4k, EOR
>
> OTOH, at sender if the send fails because PR timeout on some data
> chunk occurs i receive from the kernel not 1 but 4 notifications.
> Msg1, 4k, Notification(send failed, ssf_length=4k), EOR
> Msg2, 4k, Notification(send failed, ssf_length=4k), EOR
> Msg3, 4k, Notification(send failed, ssf_length=4k), EOR
> Msg4, 4k, Notification(send failed, ssf_length=4k), EOR
> .... some last message here to account for notification overhead ....
>
> I was expecting only the last one to have an EOR or least the
> ssf_length to be telling me there's more than 4K. Stoopid question:
> Is there some other field I should be looking at?
>
> The only way i could tell the 5 notifications are from the same
> original message is when i provide a sinfo_context at sendmsg() time.
>
>
> cheers,
> jamal
next prev parent reply other threads:[~2013-12-18 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 13:59 Send fail notifications Jamal Hadi Salim
2013-12-18 14:06 ` Jamal Hadi Salim [this message]
2013-12-18 15:20 ` Vlad Yasevich
2013-12-19 14:37 ` Jamal Hadi Salim
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=52B1ABD4.1060108@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=linux-sctp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.