* [PATCH] ath9k_htc: avoid memcpy when downloading firmware
@ 2015-03-03 4:24 Fred Chou
2015-03-03 6:00 ` Eric Dumazet
0 siblings, 1 reply; 4+ messages in thread
From: Fred Chou @ 2015-03-03 4:24 UTC (permalink / raw)
To: ath9k-devel-A+ZNKFmMK5xy9aJCnZT0Uw, kvalo-sgV2jX0FEOL9JmXXK+q4OQ,
linux-wireless-u79uwXL29TY76Z2rM5mHXA,
ath9k-devel-xDcbHBWguxHbcTqmT+pZeQ, netdev-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA
Cc: Fred Chou
From: Fred Chou <fred.chou.nd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
The temporary buffer to hold firmware data is not really needed,
and memcpy can be avoided by using data pointer instead.
Signed-off-by: Fred Chou <fred.chou.nd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
drivers/net/wireless/ath/ath9k/hif_usb.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
index 10c02f5..0bc35a8 100644
--- a/drivers/net/wireless/ath/ath9k/hif_usb.c
+++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
@@ -986,30 +986,22 @@ static int ath9k_hif_usb_download_fw(struct hif_device_usb *hif_dev)
const void *data = hif_dev->fw_data;
size_t len = hif_dev->fw_size;
u32 addr = AR9271_FIRMWARE;
- u8 *buf = kzalloc(4096, GFP_KERNEL);
u32 firm_offset;
- if (!buf)
- return -ENOMEM;
-
while (len) {
transfer = min_t(size_t, len, 4096);
- memcpy(buf, data, transfer);
err = usb_control_msg(hif_dev->udev,
usb_sndctrlpipe(hif_dev->udev, 0),
FIRMWARE_DOWNLOAD, 0x40 | USB_DIR_OUT,
- addr >> 8, 0, buf, transfer, HZ);
- if (err < 0) {
- kfree(buf);
+ addr >> 8, 0, data, transfer, HZ);
+ if (err < 0)
return err;
- }
len -= transfer;
data += transfer;
addr += transfer;
}
- kfree(buf);
if (IS_AR7010_DEVICE(hif_dev->usb_device_id->driver_info))
firm_offset = AR7010_FIRMWARE_TEXT;
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH] ath9k_htc: avoid memcpy when downloading firmware
2015-03-03 4:24 [PATCH] ath9k_htc: avoid memcpy when downloading firmware Fred Chou
@ 2015-03-03 6:00 ` Eric Dumazet
2015-03-03 14:41 ` Fred Chou
0 siblings, 1 reply; 4+ messages in thread
From: Eric Dumazet @ 2015-03-03 6:00 UTC (permalink / raw)
To: Fred Chou
Cc: ath9k-devel, kvalo, linux-wireless, ath9k-devel, netdev,
linux-kernel
On Tue, 2015-03-03 at 12:24 +0800, Fred Chou wrote:
> From: Fred Chou <fred.chou.nd@gmail.com>
>
> The temporary buffer to hold firmware data is not really needed,
> and memcpy can be avoided by using data pointer instead.
>
> Signed-off-by: Fred Chou <fred.chou.nd@gmail.com>
> ---
> drivers/net/wireless/ath/ath9k/hif_usb.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
> index 10c02f5..0bc35a8 100644
> --- a/drivers/net/wireless/ath/ath9k/hif_usb.c
> +++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
> @@ -986,30 +986,22 @@ static int ath9k_hif_usb_download_fw(struct hif_device_usb *hif_dev)
> const void *data = hif_dev->fw_data;
Here data can be vmalloc() backed.
> size_t len = hif_dev->fw_size;
> u32 addr = AR9271_FIRMWARE;
> - u8 *buf = kzalloc(4096, GFP_KERNEL);
Here buf is kmalloc() backed.
> u32 firm_offset;
>
> - if (!buf)
> - return -ENOMEM;
> -
> while (len) {
> transfer = min_t(size_t, len, 4096);
> - memcpy(buf, data, transfer);
>
> err = usb_control_msg(hif_dev->udev,
> usb_sndctrlpipe(hif_dev->udev, 0),
> FIRMWARE_DOWNLOAD, 0x40 | USB_DIR_OUT,
> - addr >> 8, 0, buf, transfer, HZ);
Are you sure usb_control_msg() accepts vmalloc()ed buffers ?
My guess is the answer is no.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] ath9k_htc: avoid memcpy when downloading firmware
2015-03-03 6:00 ` Eric Dumazet
@ 2015-03-03 14:41 ` Fred Chou
2015-03-03 14:43 ` Kalle Valo
0 siblings, 1 reply; 4+ messages in thread
From: Fred Chou @ 2015-03-03 14:41 UTC (permalink / raw)
To: Eric Dumazet
Cc: ath9k-devel, kvalo, linux-wireless, ath9k-devel, netdev,
linux-kernel
On 3/3/2015 2:00 PM, Eric Dumazet wrote:
> On Tue, 2015-03-03 at 12:24 +0800, Fred Chou wrote:
>> From: Fred Chou <fred.chou.nd@gmail.com>
>>
>> The temporary buffer to hold firmware data is not really needed,
>> and memcpy can be avoided by using data pointer instead.
>>
>> Signed-off-by: Fred Chou <fred.chou.nd@gmail.com>
>> ---
>> drivers/net/wireless/ath/ath9k/hif_usb.c | 12 ++----------
>> 1 file changed, 2 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
>> index 10c02f5..0bc35a8 100644
>> --- a/drivers/net/wireless/ath/ath9k/hif_usb.c
>> +++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
>> @@ -986,30 +986,22 @@ static int ath9k_hif_usb_download_fw(struct hif_device_usb *hif_dev)
>> const void *data = hif_dev->fw_data;
>
> Here data can be vmalloc() backed.
>
>> size_t len = hif_dev->fw_size;
>> u32 addr = AR9271_FIRMWARE;
>> - u8 *buf = kzalloc(4096, GFP_KERNEL);
>
> Here buf is kmalloc() backed.
>
>> u32 firm_offset;
>>
>> - if (!buf)
>> - return -ENOMEM;
>> -
>> while (len) {
>> transfer = min_t(size_t, len, 4096);
>> - memcpy(buf, data, transfer);
>>
>> err = usb_control_msg(hif_dev->udev,
>> usb_sndctrlpipe(hif_dev->udev, 0),
>> FIRMWARE_DOWNLOAD, 0x40 | USB_DIR_OUT,
>> - addr >> 8, 0, buf, transfer, HZ);
>
>
> Are you sure usb_control_msg() accepts vmalloc()ed buffers ?
>
> My guess is the answer is no.
>
>
I agree, and I would like to drop the patch. Thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-03-03 14:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-03 4:24 [PATCH] ath9k_htc: avoid memcpy when downloading firmware Fred Chou
2015-03-03 6:00 ` Eric Dumazet
2015-03-03 14:41 ` Fred Chou
2015-03-03 14:43 ` Kalle Valo
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).