* Re: open mac comparision
2009-06-22 9:51 open mac comparision Bharat Bhushan
@ 2009-06-23 10:07 ` Johannes Berg
0 siblings, 0 replies; 2+ messages in thread
From: Johannes Berg @ 2009-06-23 10:07 UTC (permalink / raw)
To: Bharat Bhushan; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Hi,
> i am trying to promote open source mac against
> our proprietary mac in my organization ,
There's no opensource MAC, except the Broadcom open firmware. Are you
referring to mac80211? It's not really the MAC, it's more the MLME and
some parts of the MAC. The boundaries aren't really exactly implemented
as specified.
If you were actually asking about the MAC itself, you can stop reading
here, and tell everyone that there is no open source MAC. It's not
really possible either since all hardware is different and this tends to
be implemented close to or even in the hardware.
If you're asking about the host wireless stack, read on.
> i want to make few slides
> regarding the throughput and performance related comparison.Has any
> one did any performance related study of open mac ? if not then i am
> planning to take this activity , i will measure maximum throughput
> achieve the MIPS per mbps ,if any one want to know any other
> particular point then let me know i will measure that and publisize
> the results.
I'm not aware of any speed comparison, especially obviously not compared
to your own implementation of the wireless stack. However, this question
is also quite irrelevant.
By using your own 802.11 stack, you will
* not get your driver into the kernel, which means having to maintain
the driver forever out of the tree
* not be able to take advantage of future performance work other
companies will do on the open source component
Therefore, the question doesn't make sense -- performance shouldn't be a
criterion since that will be improved. Trying to write a faster stack
might be possible, initially, but at some point you will need to catch
up with features, performance, of both, of the open source wireless
stack. At the same time, a lot of power consumption optimisation work is
going into the open source stack, something which you would have to
duplicate too, eventually.
In my opinion, asking for performance review to base such a decision on
is rather shortsighted. It might make sense to do such a review, and
then decide to improve the open source stack, so you get the best of
both worlds, but doing such a review and then deciding against it would
be painting yourself into a corner you will never get out of again
without significantly more effort.
I would suggest to start by getting your priorities right. Using the
open source stack will allow you to get a driver for Linux out easier,
will mean the community will be impressed, rather than annoyed, by you,
and finally will allow you to take advantage of future enhancements and
new standard amendments easily. Bonus points for improving the open
source stack where you think it's necessary.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread