From: RahulSrivastava 71616 <rahuls@huawei.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Query
Date: Tue, 12 Jan 2010 04:56:40 +0000 [thread overview]
Message-ID: <fa35e727bb7f.bb7ffa35e727@huawei.com> (raw)
In-Reply-To: <f9a68846db1c.db1cf9a68846@huawei.com>
Thanks!
If sendmsg succedes like this then how its possible to maintain ordering of messages:
Consider below order:
send1 ----> send2
send1 was not recieved but send2 was successfully recived by peer on same association. Application gets a notification of send1 (indicating send failed).
Regards,
Rahul
******************************************************************************************
This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it!
*****************************************************************************************
----- Original Message -----
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Monday, January 11, 2010 10:35 pm
Subject: Re: Query
To: RahulSrivastava 71616 <rahuls@huawei.com>
Cc: linux-sctp@vger.kernel.org
>
>
> RahulSrivastava 71616 wrote:
> > Hi All,
> > I have a query. When using Linux SCTP one-to-many style
> sockets sendmsg succedes even though message is not delivered at
> the peer. When I ask the socket to wait for notification it gave
> send failed in notification.
> > Is this possible for sendmsg to fail for even for one-to-many
> style socket (for peer errors)?
> >
>
> Yes. sendmsg() will return success when the data has successfully
> been accepted
> by the kernel. However, if peer has problems, you may get a
> SEND_FAILEDnotification.
>
> This is not linux SCTP specific. TCP can behave the same way
> (minus the
> notification).
>
> -vlad
>
> > Regards,
> > Rahul
> >
> >
> >
> >
> ******************************************************************************************> This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it!
> >
> *****************************************************************************************> --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> sctp" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
next prev parent reply other threads:[~2010-01-12 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 14:12 Query RahulSrivastava 71616
2010-01-11 17:05 ` Query Vlad Yasevich
2010-01-12 4:56 ` RahulSrivastava 71616 [this message]
2010-01-12 20:52 ` Query Vlad Yasevich
2011-04-05 6:30 ` Query RahulSrivastava 71616
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=fa35e727bb7f.bb7ffa35e727@huawei.com \
--to=rahuls@huawei.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 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).