Return-Path: Subject: Re: [PATCH v2 11/16] Bluetooth: Add 'eir_len' param to mgmt_device_found() From: Marcel Holtmann To: Anderson Lizardo Cc: Andre Guedes , linux-bluetooth@vger.kernel.org Date: Wed, 10 Aug 2011 17:26:57 -0700 In-Reply-To: References: <1311623405-31108-1-git-send-email-andre.guedes@openbossa.org> <1311623405-31108-12-git-send-email-andre.guedes@openbossa.org> <1312984225.3373.118.camel@aeonflux> <1312989466.3373.126.camel@aeonflux> <7E90DB69-1056-4706-9531-BA4D12199A27@openbossa.org> Content-Type: text/plain; charset="UTF-8" Message-ID: <1313022419.3373.137.camel@aeonflux> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Anderson, > > The advertising report event has the 'Length' field to inform the > > 'Data' field length, so I believe it has a variable length. > > According to its description, the 'Length' field may vary from 0x00 > > to 0x1F (31) bytes. > > You are right. Although the section 11 gives the impression the size > is always 31, this is not what happens on actual hardware, which > usually sends only the significant bytes (and the length is know from > the "Length" field. > > > The only drawback I see so far is copying extra ~200 bytes each time > > we get a advertising report data. > > I agree. If this event is being sent on each adv. data report event, > it will be more than 6 times the amount of data (with non-significant > bytes containing only zeroes) sent to userspace. if we wanna save bytes copied and send to userspace, then we might even fix this for BR/EDR. Since while it is fixed there only a fraction is used there most of the times. Regards Marcel