From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Suraj Sumangala <suraj@atheros.com>,
linux-bluetooth@vger.kernel.org, Jothikumar.Mothilal@Atheros.com
Subject: Re: [PATCH v6 1/4] add one more buffer for stream reassembly
Date: Tue, 13 Jul 2010 18:01:04 -0300 [thread overview]
Message-ID: <20100713210104.GA3106@vigoh> (raw)
In-Reply-To: <1279054151.6282.22.camel@localhost.localdomain>
Hi Marcel,
* Marcel Holtmann <marcel@holtmann.org> [2010-07-13 17:49:11 -0300]:
> Hi Suraj,
>
> > Additional reassembly buffer to keep track of stream reasembly
> >
> > Signed-off-by: Suraj Sumangala <suraj@atheros.com>
> > ---
> > include/net/bluetooth/hci_core.h | 4 ++--
> > net/bluetooth/hci_core.c | 4 ++--
> > 2 files changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
> > index 600372d..10ad3ed 100644
> > --- a/include/net/bluetooth/hci_core.h
> > +++ b/include/net/bluetooth/hci_core.h
> > @@ -66,7 +66,7 @@ struct bdaddr_list {
> > struct list_head list;
> > bdaddr_t bdaddr;
> > };
> > -
> > +#define NUM_REASSEMBLY_BUFFER 4
>
> Just call it NUM_REASSEMBLY.
>
> > struct hci_dev {
> > struct list_head list;
> > spinlock_t lock;
> > @@ -123,7 +123,7 @@ struct hci_dev {
> > struct sk_buff_head cmd_q;
> >
> > struct sk_buff *sent_cmd;
> > - struct sk_buff *reassembly[3];
> > + struct sk_buff *reassembly[NUM_REASSEMBLY_BUFFER];
> >
> > struct mutex req_lock;
> > wait_queue_head_t req_wait_q;
> > diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
> > index aeb2982..5df09fd 100644
> > --- a/net/bluetooth/hci_core.c
> > +++ b/net/bluetooth/hci_core.c
> > @@ -914,7 +914,7 @@ int hci_register_dev(struct hci_dev *hdev)
> > skb_queue_head_init(&hdev->cmd_q);
> > skb_queue_head_init(&hdev->raw_q);
> >
> > - for (i = 0; i < 3; i++)
> > + for (i = 0; i < NUM_REASSEMBLY_BUFFER; i++)
> > hdev->reassembly[i] = NULL;
> >
> > init_waitqueue_head(&hdev->req_wait_q);
> > @@ -973,7 +973,7 @@ int hci_unregister_dev(struct hci_dev *hdev)
> >
> > hci_dev_do_close(hdev);
> >
> > - for (i = 0; i < 3; i++)
> > + for (i = 0; i < NUM_REASSEMBLY_BUFFER; i++)
> > kfree_skb(hdev->reassembly[i]);
> >
> > hci_notify(hdev, HCI_DEV_UNREG);
>
> And don't forget to modify the __reassembly macro to do -1 instead of -2
> now. Since we said we keep the [0] for the stream reassembly.
The __reassembly macro is removed in the following patches.
--
Gustavo F. Padovan
http://padovan.org
next prev parent reply other threads:[~2010-07-13 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 9:33 [PATCH v6 1/4] add one more buffer for stream reassembly Suraj Sumangala
2010-07-13 9:33 ` [PATCH v6 2/4] Implements hci_reassembly to reassemble Rx packets Suraj Sumangala
2010-07-13 9:33 ` [PATCH v6 3/4] Modified hci_recv_fragment() to use hci_reassembly Suraj Sumangala
2010-07-13 9:33 ` [PATCH v6 4/4] Implemented HCI frame reassembly for Rx from stream Suraj Sumangala
2010-07-13 20:49 ` [PATCH v6 1/4] add one more buffer for stream reassembly Marcel Holtmann
2010-07-13 21:01 ` Gustavo F. Padovan [this message]
2010-07-13 21:03 ` Marcel Holtmann
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=20100713210104.GA3106@vigoh \
--to=gustavo@padovan.org \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=suraj@atheros.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).