linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit K Bag <amit.k.bag@intel.corp-partner.google.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: OPP throughput is low in ubuntu 18.04
Date: Fri, 14 Feb 2020 07:51:04 +0530	[thread overview]
Message-ID: <CAANRJty7xZ+GNyAU82oXAdCuJ07LnaZm_M2yUet3rfgwd6AVMA@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZJccLD-BD1aAB70sX9_FqSwkDc789-WQhi0V4Udbp5wBA@mail.gmail.com>

Hello Luiz,

I am not sure what changes in kernel causing low throughput. If I get
any clue I will let you know.
I wil lalso test your patch with linux - linux and update the result.

On Fri, Feb 14, 2020 at 6:18 AM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Amit,
>
> On Thu, Feb 13, 2020 at 3:32 AM Amit K Bag
> <amit.k.bag@intel.corp-partner.google.com> wrote:
> >
> > Hello Luiz,
> >
> > I tested with the patch you have mentioned but not getting any better
> > throughput.
> > Please have a look at the log attached.
> >
> > We are using below configuration for linux
> > - Kernel : 4.19.102
> > - OS : ubuntu 18.04.2 LTS
> > - Bluez -5.48
> >
> > For other machine we are using windows
>
> I think there is some work to be done to work with RFCOMM since we are
> only doing this for L2CAP, I will have a look later this week, btw
> have you look into any difference we may have between these kernels?
> Or actually in what combination they appear because there could be an
> isolated problem in either the kernel or the userspace changes.
>
> > On Mon, Feb 10, 2020 at 11:03 PM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> > >
> > > Hi Amit,
> > >
> > > On Mon, Feb 10, 2020 at 3:20 AM Amit K Bag
> > > <amit.k.bag@intel.corp-partner.google.com> wrote:
> > > >
> > > > Hello All,
> > > >
> > > > I am tring to test the OPP throughput in linux.
> > > > I transferred between 2 machines having ubuntu 16.04 with bluez
> > > > version 5.44 in that I am getting 1.4mbps speed.
> > > >
> > > > Kernel : 4.14.13
> > > > OS : ubuntu 18.04.2 LTS
> > > > Bluez -5.44
> > > >
> > > > I am using a 12 MB of audio file.
> > > > But the same file when I transferred between  2 machines having ubuntu
> > > > 18.04 the speed is significantly reduced.
> > > >
> > > > Kernel : 4.18.0-15-generic
> > > > OS : ubuntu 18.04.2 LTS
> > > > Bluez -5.48
> > > >
> > > > Could someone tell me why its reduced in ubuntu 18.04
> > >
> > > I don't think we change anything on Obexd related to that so perhaps
> > > it is something related to the L2CAP MTU? We could try setting the MTU
> > > to 0 so it automatically picks the matching MTU if you do have the
> > > following patch applied to your kernel:
> > >
> > > Bluetooth: Auto tune if input MTU is set to 0
> > >
> > >
> > > --
> > > Luiz Augusto von Dentz
>
>
>
> --
> Luiz Augusto von Dentz

  reply	other threads:[~2020-02-14  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 11:19 OPP throughput is low in ubuntu 18.04 Amit K Bag
2020-02-10 17:33 ` Luiz Augusto von Dentz
     [not found]   ` <CAANRJtxFLMU6i4maUgpLC1iar1Q9HJv+ELcwpQv=c4bLo-uPAQ@mail.gmail.com>
2020-02-14  0:48     ` Luiz Augusto von Dentz
2020-02-14  2:21       ` Amit K Bag [this message]
2020-02-26  5:18         ` Amit K Bag

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=CAANRJty7xZ+GNyAU82oXAdCuJ07LnaZm_M2yUet3rfgwd6AVMA@mail.gmail.com \
    --to=amit.k.bag@intel.corp-partner.google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).