From: Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com>
To: Hariprasad Kelam <hariprasad.kelam@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: How to debug throughput issues?
Date: Wed, 26 Jun 2019 10:56:26 +0530 [thread overview]
Message-ID: <CAPY=qRRKzYYT6r55KgMhQGvMAjqg0TNEGik29y7NE=gnpUtQhw@mail.gmail.com> (raw)
In-Reply-To: <20190626021444.GA2588@hari-Inspiron-1545>
On Wed, Jun 26, 2019 at 7:44 AM Hariprasad Kelam
<hariprasad.kelam@gmail.com> wrote:
>
> On Tue, Jun 25, 2019 at 10:26:54PM +0530, Subhashini Rao Beerisetty wrote:
> Hi Subhashini,
>
> Please see inline,
> > Hi All,
> >
> > I’ve two Bluetooth dongles and connected to two Linux
> > systems(hostname1, hostname2). I’ve a test executable and it creates a
> > BT link does the file transfer and calculates the throughput.
> >
> Are these dongle supports classic mode or Ble?
It supports classic mode.
> Which profile are you using to establish connection between these two? (
> PAN, ..etc)
> > I repeated the same test with the same BT dongles on another
> > different Linux systems(hostname3, hostname4), here I’m getting less
> > data rate.
> >
> After inserting dongles to host are you getting serial interface
> /dev/tty* or hci interface ?
Using serial interface /dev/tty*
> If its hci interface ,you can use hcidump to see packets and check MTU
> size
> > Here first I want to narrow down whether the issue is below device
> > driver level or above device driver level and where the bottleneck is?
> > which tools will help me to debug this kind of issue?
> >
> I think before jumping into driver level ,its better to ensure all
> bluetooth parameters are same on both the setups.
Except the kernel version(hostname1 & 2 are having same kernel and it
differs with hostname3 & 4 kernel version) rest all other stuff is
same. So I'd like to know how to know which part of kernel mode
functions causing more delay and any tools are there to debug these
issues?
>
> Thanks,
> Hariprasad k
> > Thanks
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies@kernelnewbies.org
> > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-06-26 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 16:56 How to debug throughput issues? Subhashini Rao Beerisetty
2019-06-26 2:14 ` Hariprasad Kelam
2019-06-26 5:26 ` Subhashini Rao Beerisetty [this message]
2019-06-26 5:47 ` hariprasad kelam
2019-06-26 5:52 ` Subhashini Rao Beerisetty
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='CAPY=qRRKzYYT6r55KgMhQGvMAjqg0TNEGik29y7NE=gnpUtQhw@mail.gmail.com' \
--to=subhashbeerisetty@gmail.com \
--cc=hariprasad.kelam@gmail.com \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).