netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fred Chou <fred.chou.nd@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: ath9k-devel@qca.qualcomm.com, kvalo@codeaurora.org,
	linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k_htc: avoid memcpy when downloading firmware
Date: Tue, 03 Mar 2015 22:41:23 +0800	[thread overview]
Message-ID: <54F5C813.4030505@gmail.com> (raw)
In-Reply-To: <1425362407.5130.161.camel@edumazet-glaptop2.roam.corp.google.com>



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.

  reply	other threads:[~2015-03-03 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2015-03-03 14:43     ` Kalle Valo

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=54F5C813.4030505@gmail.com \
    --to=fred.chou.nd@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).