linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Manoj Sharma <ursmanoj@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
	Anurag Gupta <anurag.gupta@stericsson.com>
Subject: Re: [PATCH 0/2] Support for reserving bandwidth on L2CAP socket
Date: Fri, 27 Jul 2012 07:37:43 -0700	[thread overview]
Message-ID: <1343399863.1803.10.camel@aeonflux> (raw)
In-Reply-To: <CAHH5__6sQ2yyEpuDZYMd4mFmHJEJeRX4eKzVM47k9TQcSthywA@mail.gmail.com>

Hi Manoj,

> >> These patches allows L2CAP socket user to reserve bandwidth in
> >> percentage. Underlying socket reserves calculated number of
> >> HCI credits for this L2CAP channel.
> >
> > this description is by far not enough. Explain why you are doing this.
> > And make it a detailed description. Preferable with hcidump traces
> > showing why this makes a difference at all.
> >
> This patch simply adds an additional L2CAP socket option for reserving
> bandwidth.
> The reserved bandwidth would result into reserving calculated number
> of ACL data credits. Thus the L2CAP channels without this option set
> would not be able to use all available ACL buffers in controller. This
> would ensure that whenever an L2CAP channel with this option set has
> data to send, it does not starve or wait because of other channels
> already using all controller buffers.
> 
> Above explanation is most suitable in case when simultaneous AVDTP
> streaming channels and other channels (e.g. OPP, PBAP etc) are in
> action. Such an arrangement for reserving credits would allow AVDTP
> stream to flow to controller without any obstacle from simultaneous
> traffic and help removing glitches in music streaming over Bluetooth.
> Please suggest if this description is sufficient and if I should push
> patch-set again.

and what is the problem with using SO_PRIORITY for this?

Regards

Marcel



  reply	other threads:[~2012-07-27 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  9:54 [PATCH 0/2] Support for reserving bandwidth on L2CAP socket Manoj Kumar Sharma
2012-07-24  9:54 ` [PATCH 1/2] Bluetooth: Usage of HCI channels in L2CAP Manoj Kumar Sharma
2012-07-24  9:55   ` [PATCH 2/2] Bluetooth: L2CAP socket option to reserve bandwidth Manoj Kumar Sharma
2012-07-24 13:53 ` [PATCH 0/2] Support for reserving bandwidth on L2CAP socket Marcel Holtmann
2012-07-27  5:14   ` Manoj Sharma
2012-07-27 14:37     ` Marcel Holtmann [this message]
2012-07-30  6:30       ` Manoj Sharma
2012-07-30 16:11         ` Luiz Augusto von Dentz
2012-07-31 11:30           ` Manoj Sharma
2012-07-31 14:10             ` Luiz Augusto von Dentz
2012-07-31 16:58               ` Mat Martineau
2012-08-01 17:26                 ` Luiz Augusto von Dentz
2012-08-13  6:14                   ` Manoj Sharma

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=1343399863.1803.10.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=anurag.gupta@stericsson.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ursmanoj@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).