From: lukasz <ru-dy@o2.pl>
To: linux-bluetooth@vger.kernel.org
Subject: l2cap - packet handled event
Date: Mon, 11 Jan 2010 16:56:05 +0100 [thread overview]
Message-ID: <1263225365l.20825l.7l@jars-desktop> (raw)
I'm sorry if I write this msg in wrong place or wrong format.
I'm using bluez (l2cap connection) and all my operations are using
socket API. I have problem with latencies and I would like to know,
when my packet was sent. Is there any possibility to subscribe with
function handler or get "packet handled" event from the stack ? In my
case I don't want to send next packet, if the previous one is not sent
( I don't want buffer them, throughput can be limited, I need minimal
latencies). Is there any possibility to limit socket buffer size (2nd
write to socket will block, when I will try to write 2nd packet, before
1st is not sent) ?
best regards,
sorry for my English
next reply other threads:[~2010-01-11 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 15:56 lukasz [this message]
2010-01-11 16:41 ` l2cap - packet handled event Gustavo F. Padovan
2010-01-11 16:42 ` Gustavo F. Padovan
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 15:41 lukasz
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=1263225365l.20825l.7l@jars-desktop \
--to=ru-dy@o2.pl \
--cc=linux-bluetooth@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