From: "Mingfan.Lu" <lucharse@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: ml@felicis.org
Subject: Re: [Bluez-devel] the effect of linux 2.6.18 to the bluez
Date: Tue, 14 Nov 2006 14:43:33 +0800 [thread overview]
Message-ID: <3f5a9ba20611132243l173f149br90ffb8401c1c3396@mail.gmail.com> (raw)
In-Reply-To: <1161284638.7885.11.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 2638 bytes --]
Martin,
I have done some tests like you mentioned.
A real machine (P4 3.0G+1G RAM)
Debian Linux (original kernel 2.6.8)
Bluez 3.6
I have rebuilt the kernels in debian way:
2.6.16.13-4 from opensuse 10.1
2.6.17 from kernel.org
2.6.18 from kernel org
2.6.18-mh7 (with the patch mh7 from
bluez)
The speed of OBEX is similar, but still low. about 5Kps. < 15~30 Kps (Your
results.)
I don't know why.
The configure?
Could you give me your .config file when you build the kernel.
Thank you very much.
2006/10/20, Martin Röhricht <ml@felicis.org>:
>
> Am Donnerstag, den 19.10.2006, 16:07 +0800 schrieb Mingfan.Lu:
>
> > 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?
>
> I build the kernels the "debian way" cause I use Ubuntu as well. So
> basically:
> (1) tar xjf linux-2.6.18.x.tar.bz2
> (2) cd linux-2.6.18.x
> (3) patch -p1 < ../patch-2.6.18-mh6
> (4) cp /boot/config-2.6.15-26-686 .config
> (5) make oldconfig
> [edit some config options manually if necessary]
> (6) fakeroot make-kpkg kernel_image modules_image --initrd --revision
> mh6 binary
> (7) cd ..
> (8) dpkg -i kernel-image-2.6.18.xmh6_i386.deb
>
> Edit /boot/grub/menu.lst if necessary and that's it.
> Your problems are really strange. How do you measure the time? I don't
> think it has anything to do with the config file per se. But I know of
> some pretty neat and improved debugging facilities -- maybe you want to
> check out that there is nothing in action that slows down the machine
> just for the purpose of deadlock detections.
>
> I'm sorry about it, but it seems extremely hard to me locating such a
> problem that never affects one of my machines. :-/
>
> Good luck,
> 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: 4374 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
prev parent reply other threads:[~2006-11-14 6:43 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
2006-10-19 19:03 ` Martin Röhricht
2006-11-14 6:43 ` Mingfan.Lu [this message]
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=3f5a9ba20611132243l173f149br90ffb8401c1c3396@mail.gmail.com \
--to=lucharse@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ml@felicis.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