linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Bluetooth: L2CAP: Improve credits logic
Date: Thu, 27 Sep 2018 12:52:50 +0200	[thread overview]
Message-ID: <136C6167-7F57-4CF5-AEFD-DC54BDBFDFA3@holtmann.org> (raw)
In-Reply-To: <20180904103922.25504-1-luiz.dentz@gmail.com>

Hi Luiz,

> These changes replace the existing threshold logic with a limpler logic
> that gives back credits after receiving an SDU. It also removes the
> debugfs entries to configure the MPS and credits with auto selected one
> derived from the MTU and MPS.
> 
> v2: Account from the SDU length when adjusting the MPS.
> 
> Luiz Augusto von Dentz (3):
>  Bluetooth: L2CAP: Derive MPS from connection MTU
>  Bluetooth: L2CAP: Derive rx credits from MTU and MPS
>  Bluetooth: L2CAP: Detect if remote is not able to use the whole MPS
> 
> include/net/bluetooth/l2cap.h |  3 --
> net/bluetooth/l2cap_core.c    | 66 +++++++++++++++++++++++------------
> 2 files changed, 44 insertions(+), 25 deletions(-)

all 3 patches have been applied to bluetooth-next tree.

Regards

Marcel


      parent reply	other threads:[~2018-09-27 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 10:39 [PATCH v2 0/3] Bluetooth: L2CAP: Improve credits logic Luiz Augusto von Dentz
2018-09-04 10:39 ` [PATCH v2 1/3] Bluetooth: L2CAP: Derive MPS from connection MTU Luiz Augusto von Dentz
2018-09-04 10:39 ` [PATCH v2 2/3] Bluetooth: L2CAP: Derive rx credits from MTU and MPS Luiz Augusto von Dentz
2018-09-04 10:39 ` [PATCH v2 3/3] Bluetooth: L2CAP: Detect if remote is not able to use the whole MPS Luiz Augusto von Dentz
2018-09-20  9:26 ` [PATCH v2 0/3] Bluetooth: L2CAP: Improve credits logic Luiz Augusto von Dentz
2018-09-27 10:52 ` Marcel Holtmann [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=136C6167-7F57-4CF5-AEFD-DC54BDBFDFA3@holtmann.org \
    --to=marcel@holtmann.org \
    --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).