From: "Mingfan.Lu" <lucharse@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] the effect of linux 2.6.18 to the bluez
Date: Thu, 19 Oct 2006 16:07:36 +0800 [thread overview]
Message-ID: <3f5a9ba20610190107je24b0bbg6bd5da0a05f6e0f2@mail.gmail.com> (raw)
In-Reply-To: <1161000951.10392.26.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 4798 bytes --]
Hi, Martin,
Thank you for you nice help.
I retest it in a ubuntu machine (kernel version 2.6.15), bluez lib's
version is 2.24
Then I rebuilt 2.6.18 in the ubuntu machine.
I still found that 2.6.18 is much slower than 2.6.15 when pushing obex over
bluez.
when I rebuit 2.6.18 in the 2.6.15 kernel machine:
make mrproper
make oldconfig (use default value for every new config)
make
make modules_install
make install
mkinitramfs -o /boot/initrd.img-2.6.18 2.6.18
I don't know whether the config make it happen or there is something wrong
with it?
So, Martin, How about you make config when you building your new kernel?
Thanks very much.
==============================================
2006/10/16, Martin Röhricht <ml@felicis.org>:
>
> Am Montag, den 16.10.2006, 13:25 +0800 schrieb Mingfan.Lu:
> > the following is my test result in a real machine:
> > [...]
>
> Okay, due to your tenacious demand, I compiled and installed a plain
> 2.6.18.1 vanilla kernel as well as a 2.6.18.1 kernel with the latest
> -mh5 patch applied.
> I will show you my test results for two files, the first being 1376034
> bytes (1,31MB) in size and the second being 2397995 bytes (2,29MB) in
> size.
> Let me at first mention the results that I got. I didn't encounter any
> slowness by using a 2.6.18.1 vanilla kernel. However it looks like the
> newly introduced and applied flow control may slow down the transfer
> speed. But be aware that (L2CAP) flow control mode is in action only by
> using two Linux kernels that have one of the latest -mh* patches
> applied! This mode is not(!) used by transmission between a Linux
> computer and another one that uses a proprietary Bluetooth software
> stack (even if the new Symbian OS may be able to use flow control mode,
> too), or say two Linux computers of which one has a kernel without this
> new patch applied.
> You didn't specify your exact settings -> did you apply one of the
> latest -mh* patches to you 2.6.18 kernel or not? Which computers did you
> use (one is the Linux computer but who is the other one)?
>
> So here are my results. The first three tests were done between a Linux
> computer and an Apple iMac G4 with the Apple Bluetooth stack that comes
> with Mac OS X 10.4:
>
> Test with kernel 2.6.18.1 and Apple Bluetooth Stack:
> Retrieval:
> 1376034 bytes -> 58 sec -> 23KB/s
> 2397995 bytes -> 95 sec -> 25KB/s
>
> Transmission:
> 1376034 bytes -> 42 sec -> 32KB/s
> 2397995 bytes -> 73 sec -> 32KB/s
>
>
> Test with kernel 2.6.15 (Ubuntu Dapper Drake) and Apple Bluetooth Stack:
> Retrieval:
> 1376034 bytes -> 57 sec -> 24KB/s
> 2397995 bytes -> 99 sec -> 24KB/s
>
> Transmission:
> 1376034 bytes -> 46 sec -> 29KB/s
> 2397995 bytes -> 77 sec -> 30KB/s
>
>
> Test with kernel 2.6.18.1-mh5 and Apple Bluetooth Stack:
> Retrieval:
> 1376034 bytes -> 54 sec -> 25KB/s
> 2397995 bytes -> 94 sec -> 25KB/s
>
> Transmission:
> 1376034 bytes -> 43 sec -> 31KB/s
> 2397995 bytes -> 73 sec -> 32KB/s
>
>
> ------------(now between two Linux computers)---------
> Test with kernel 2.6.18.1-mh5 to kernel 2.6.18.1-mh5
> Retrieval:
> 1376034 bytes -> 88 sec -> 15KB/s
> 2397995 bytes -> 154 sec -> 15KB/s
>
> Transmission:
> 1376034 bytes -> 82 sec -> 16KB/s
> 2397995 bytes -> 140 sec -> 17KB/s
>
>
> Test with kernel 2.6.18.1-mh5 to kernel 2.6.15 (Ubuntu Dapper Drake)
> Retrieval:
> 1376034 bytes -> 57 sec -> 24KB/s
> 2397995 bytes -> 99 sec -> 24KB/s
>
> Transmission:
> 1376034 bytes -> 68 sec -> 20KB/s
> 2397995 bytes -> 114 sec -> 21KB/s
>
>
> As you can see -- the transmission speed is quite constant between the
> same setups. Two things would need more investigations:
> (1) Why is it that a file transfer from Linux to Apple is faster than
> between two Linux entities?
> (2) Is it really L2CAP Flow Control Mode that slows down the connection
> with its protocol overhead?
>
> If Flow Control Mode really slows down the connection, we should try to
> implement a user interface to enable or disable this mode. But currently
> this is not urgent as no other device makes use of it.
>
> Martin
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> 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: 5921 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- 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-19 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 5:25 [Bluez-devel] the effect of linux 2.6.18 to the bluez Mingfan.Lu
2006-10-16 12:15 ` Martin Röhricht
2006-10-16 16:21 ` Mingfan.Lu
2006-10-19 8:07 ` Mingfan.Lu [this message]
2006-10-19 19:03 ` Martin Röhricht
2006-11-14 6:43 ` 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=3f5a9ba20610190107je24b0bbg6bd5da0a05f6e0f2@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