From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
luciano.coelho@nokia.com, Bob Copeland <me@bobcopeland.com>,
linux-wireless@vger.kernel.org
Subject: Re: wl12xx: third submission
Date: Thu, 23 Apr 2009 21:02:35 +0300 [thread overview]
Message-ID: <87zle76yf8.fsf@litku.valot.fi> (raw)
In-Reply-To: <1240509453.30082.265.camel@johannes.local> (Johannes Berg's message of "Thu\, 23 Apr 2009 19\:57\:33 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2009-04-23 at 20:49 +0300, Kalle Valo wrote:
>
>> No problem, I can update wl12xx as soon as you finalise the interface.
>> Just let me know.
>
> Well, I just posted it earlier as [PATCH] :)
Thanks, I'll start working on it tomorrow.
>> > how about IPv4 alignment? Could you read the packet header first,
>> > memmove that and then read the rest, i.e. do two wl12xx_spi_mem_read
>> > calls? Might or might not be more efficient...
>>
>> SPI access add latency, it would be faster to read as much as possible
>> in one transaction.
>
> Question is how it measures against the CPU doing memmove() on the
> entire frame when necessary.
I don't have any numbers, but for example omap2_mcspi is scheduling
processes etc. so I would say that memmove() is cheaper. Does anyone
have more knowledge about this?
>> Is there anything which in your opinion prevents inclusion to
>> wireless-testing?
>
> Give that you and Bob are working on it, I don't think so. Except the
> API issue, which means it won't compile when John merges my patch.
The compilation fix is easy to solve, I'll take care of it.
Thanks for your comments.
--
Kalle Valo
prev parent reply other threads:[~2009-04-23 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:40 wl12xx: third submission Kalle Valo
2009-04-23 17:32 ` Johannes Berg
2009-04-23 17:49 ` Kalle Valo
2009-04-23 17:57 ` Johannes Berg
2009-04-23 18:02 ` Kalle Valo [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=87zle76yf8.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luciano.coelho@nokia.com \
--cc=me@bobcopeland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.