From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] SCO flow control
Date: Fri, 09 Jun 2006 19:05:48 +0200 [thread overview]
Message-ID: <4489AA6C.7010300@free.fr> (raw)
In-Reply-To: <1149712246.22472.56.camel@localhost>
Hi Marcel,
>>> Another question is if we really should queue the data in sk_write_queue
>>> and not directly in the core. I would prefer to send the data to the
>>> core and then stream it from there.
>> That's an interesting question... :-)
>> I asked it myself when i started to design this feature.
>> In fact having outgoing packets stored in a socket queue has some
>> advantages:
>> * it makes use of the BSD socket send queue, and thus can reuse some
>> generic socket queue management related functions, which rely on some
>> well known sk_buff variable (sk_sndbuff, sk_wmem_alloc, sk_rcvbuff,
>> sk_rmem_alloc ...)
>> * it makes the thing symetrical, both uplink and downlink path make
>> use socket queues to buffer data.
>>
>> As such I thought there were not any valid reason to put in the core...
>> however if you have suggestions i would be very happy to hear them. :-)
>
> Actually I never thought about SCO as socket is the best interface. So
> we might wanna move away from it sometime in the future. And in this
> case it would be great if it uses simple SKB queues or maybe kfifo for
> it. Even if this sounds like more work right now, I might be worth it.
It might make sense: however we must take into account the following
constraints:
- we must be aple to setup fifo lengths from userspace, so that to
simulate a variable size ring buffer as found on sound card hardware.
- we must be able to put the sending task to sleep, and wake it up
later, when the fifo gets 'full'.
I'm not against this, even if it means more work...
However i don't have any precise idea on which communication mechanism
to use between userspace/kernelspace. Any ideas ??
>
> Let's have another patch on top of 2.6.16-mh1 and maybe you also wanna
> adapt scotest for testing it.
>
Ok, i'm gonna work on that then...
Cheers,
Fabien
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-09 17:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 19:46 [Bluez-devel] [PATCH] SCO flow control Fabien Chevalier
2006-05-29 20:33 ` Marcel Holtmann
2006-05-29 21:39 ` Pieter Poorthuis
2006-05-29 22:21 ` Marcel Holtmann
2006-05-30 13:28 ` Fabien Chevalier
2006-06-01 19:15 ` Marcel Holtmann
2006-06-07 20:15 ` Fabien Chevalier
2006-06-07 20:30 ` Marcel Holtmann
2006-06-09 17:05 ` Fabien Chevalier [this message]
2006-06-09 20:17 ` Marcel Holtmann
2006-06-10 9:24 ` Fabien Chevalier
2006-06-10 22:22 ` Marcel Holtmann
2006-06-10 9:59 ` Fabien Chevalier
2006-06-10 23:14 ` Marcel Holtmann
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=4489AA6C.7010300@free.fr \
--to=fabchevalier@free.fr \
--cc=bluez-devel@lists.sourceforge.net \
/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.