From: "Mingfan.Lu" <lucharse@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] About the kernel 2.6.18
Date: Sun, 8 Oct 2006 14:13:04 +0800 [thread overview]
Message-ID: <3f5a9ba20610072313w41cb4aa1qf0b5a21a7199f737@mail.gmail.com> (raw)
In-Reply-To: <1159972670.1601.25.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1692 bytes --]
Hi,
I have rebuilt the 2.6.17, the speed is good. so, I don't know why
2.6.18makes the RFCOMM socket communication slower.
Who can have a try to compare the speed using different kernel ?
Need your nice help. :)
2006/10/4, Marcel Holtmann <marcel@holtmann.org>:
>
> Hi,
>
> >
> > My oepnsuse 10.1 with the default kernel 2.6.16.13-4.
> > When 2.6.18-mh3 released, I rebuilt and updated the kernel to
> > 2.6.18 and then patched it.
> > When Holtman released the patch for handling multiple l2cap
> > connections, I patched the new kernel .
> > But at last, I found that the speed of the OBEX pushing and other
> > Rfcomm socket communications is slower than the original kernel.
> > Then I rebuilt the 2.6.18 without the 2.6.18-mh3 and the patch for
> > handling multiple l2cap connections, I found it is still slower.
> > So I think the patch is not the reason.
> > But what makes the bluetooth communication slower? The new kernel
> > version 2.6.18?
>
> if the 2.6.18 kernel is slower, then it must be something else. You
> might wanna test with a 2.6.17 kernel.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
--
With respects,
Mingfan.Lu
[-- Attachment #1.2: Type: text/html, Size: 2475 bytes --]
[-- Attachment #2: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-08 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f5a9ba20609291930r5b4e4c97g8b33901666fef491@mail.gmail.com>
2006-10-02 16:46 ` [Bluez-devel] About the kernel 2.6.18 Mingfan.Lu
2006-10-04 14:37 ` Marcel Holtmann
2006-10-08 6:13 ` Mingfan.Lu [this message]
2006-10-08 13:29 ` Marcel Holtmann
2006-10-09 2:57 ` Mingfan.Lu
2006-10-09 9:04 ` Stefan Seyfried
2006-10-09 9:38 ` Mingfan.Lu
2006-10-09 9:39 ` Mingfan.Lu
2006-10-09 9:49 ` Peter Wippich
2006-10-09 9:47 ` Marcel Holtmann
2006-10-09 11:57 ` Mingfan.Lu
2006-10-11 8:30 ` Mingfan.Lu
2006-10-12 2:23 ` Mingfan.Lu
2006-10-13 4:17 ` Fwd: " Mingfan.Lu
2006-10-03 14:55 ` Mingfan.Lu
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=3f5a9ba20610072313w41cb4aa1qf0b5a21a7199f737@mail.gmail.com \
--to=lucharse@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox