From: Tristan Lelong <tristan@lelong.xyz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org,
Tristan Lelong <tlelong@adeneo-embedded.us>
Subject: Re: [PATCH 2/2] bcsp: Change tx window size in configuration
Date: Fri, 12 Dec 2014 22:28:55 -0800 [thread overview]
Message-ID: <20141213062855.GB3058@localhost.localdomain> (raw)
In-Reply-To: <4DDEED41-D60D-47D0-9AB6-6FD43A0BCE0C@holtmann.org>
On Fri, Dec 12, 2014 at 02:58:30PM +0100, Marcel Holtmann wrote:
Hi Marcel,
> >
> > +config BT_HCIUART_BCSP_WINSIZE
> > + int "BCSP reliable packet TX window size"
> > + default 4
> > + depends on BT_HCIUART_BCSP
> > + help
> > + Defines the number of packets that can be sent before receiving a ACK.
> > +
>
> I would prefer if we get a bit more help text here.
>
Yes, I can make it a bit more explicit and descriptive.
> >
> > - if (bcsp->unack.qlen < BCSP_TXWINSIZE) {
> > + if (bcsp->unack.qlen < CONFIG_BT_HCIUART_BCSP_WINSIZE) {
> > skb = skb_dequeue(&bcsp->rel);
> > if (skb != NULL) {
> > struct sk_buff *nskb = bcsp_prepare_pkt(bcsp, skb->data, skb->len,
>
> This is fine with me, but we might also want to add a module parameter to allow changing it. If people want to play with it then they do not need to rebuild their module.
>
> Another alternative is to provide an ioctl for changing it.
That makes sense, I think a parameter is a good solution, and if nobody shows any preference, I'll implement it this way.
Thanks
prev parent reply other threads:[~2014-12-13 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 7:14 [PATCH 0/2] BCSP Link Establishment in kernel Tristan Lelong
2014-12-12 7:14 ` [PATCH 1/2] hci_bcsp: Add LE protocol on kernel side Tristan Lelong
2014-12-12 13:58 ` Marcel Holtmann
2014-12-13 6:26 ` Tristan Lelong
2014-12-17 9:23 ` Tristan Lelong
2014-12-12 7:14 ` [PATCH 2/2] bcsp: Change tx window size in configuration Tristan Lelong
2014-12-12 13:58 ` Marcel Holtmann
2014-12-13 6:28 ` Tristan Lelong [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=20141213062855.GB3058@localhost.localdomain \
--to=tristan@lelong.xyz \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=tlelong@adeneo-embedded.us \
/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).