Re: where is (if at all) ioctl support for sctp...?

[Vlad Yasevich <vladislav.yasevich@hp.com>]

leon zadorin wrote:
> Hi all,
> my system is
> 2.6.23.1-42.fc8 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
> as I understand it - it comes with the kernel that is already
> sctp-enabled... (in fact I am able to create sctp sockets and
> communicate data between them).
> 
> I have a question wrt ability of finding the amount of 'free space' in
> the SND buffer associated with a givent sctp socket's fd (the actual
> buffering strategy [single buffer per association or not] is not
> important to me - only the fact that eventually any message written
> via an SCTP socket will have to go to some kernel-level buffer - and I
> want to know the amount of free space left in such a buffer before
> actually writing the message).
> 
> Essentially I don't want to wait for 'would block' type of a response
> from a written socket as in my deployment scenario it would,
> essentially, be too late- I want to begin throttling the data rate
> being directed to the outgoing sctp socket based on the amount of free
> space available in socket's buffer (the exact reasons are not that
> important and will not benefit this discussion).
> 
> This is present in TCP protocols with ioctls like SIOCOUTQ.
> 
> This is also available in SCTP's implelmentation by OpenSS7 (sctp-0.2.26)...
> 
> So just to clear a few things:
> 1) is linux's default SCTP implementation in 2.6 different from
> OpenSS7 implementation?

Yes, very different.

> 2) if so - are there any plans to support the aforementioned ioctl?

There are no plans that I know off.  This is the first such question/request,
so feel free to implement it and contribute the code.

-vlad
> 
> kind regards
> Leon.
> --
> 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
>