netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Simon Barber <simon@devicescape.com>
Cc: Jiri Benc <jbenc@suse.cz>,
	Johannes Berg <johannes@sipsolutions.net>,
	netdev <netdev@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Michael Buesch <mbuesch@freenet.de>,
	Ivo van Doorn <ivdoorn@gmail.com>,
	Michael Wu <flamingice@sourmilk.net>,
	Jouni Malinen <jkm@devicescape.com>,
	Daniel Drake <dsd@gentoo.org>, Hong Liu <hong.liu@intel.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	James Ketrenos <jketreno@linux.intel.com>,
	David Kimdon <dwhedon@devicescape.com>,
	Udayan Singh <udayan.singh@gmail.com>
Subject: Re: wireless notes / pre d80211 merge
Date: Wed, 15 Nov 2006 13:46:25 -0500	[thread overview]
Message-ID: <455B6081.2030003@pobox.com> (raw)
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29F0192722C@dhost002-46.dex002.intermedia.net>

Simon Barber wrote:
> I disagree that the master device is a hack - I also disagree that we
> should use 802.11 format frames anywhere but internally inside the
> 802.11 stack. The 802.11 specification does not use 802.11 format frames
> to communicate with the upper layers - it uses almost exactly the same
> interface as 802.3 ethernet does. This is a 2 address interface. I

The 802.11 specification doesn't communicate with any layer :)  The 
Linux kernel code in question does that.

In Linux it is generally bad form to emulate something (802.3 ethernet, 
in this case).  Overhead increases, performance decreases, and there are 
inevitably emulation bugs.

802.11 /is not ethernet/, and you are already breaking assumptions by 
pretending that it is.


> It is normal to have a single interface to represent the physical
> hardware network interface. This is exactly the pattern that many other
> physical network devices use. Things like sniffing should go on on this
> physical interface - and the changes that johannes proposes are exactly
> the right things to enable this.

Sure... when it behaves like a normal interface.  Stuff like "TX goes 
through the interface, but not RX" is definitely /not/ normal.

	Jeff



  parent reply	other threads:[~2006-11-15 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 22:19 wireless notes / pre d80211 merge Johannes Berg
2006-11-15  0:11 ` Jiri Benc
2006-11-15  2:10   ` Simon Barber
2006-11-15  9:43     ` Jiri Benc
2006-11-15 10:13       ` Johannes Berg
2006-11-15 18:47       ` Jeff Garzik
2006-11-15 10:03     ` Johannes Berg
2006-11-15 18:46     ` Jeff Garzik [this message]
2006-11-15  9:16   ` Johannes Berg
2006-11-15 10:05     ` Jiri Benc
2006-11-15 10:16       ` Johannes Berg

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=455B6081.2030003@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dsd@gentoo.org \
    --cc=dwhedon@devicescape.com \
    --cc=flamingice@sourmilk.net \
    --cc=hong.liu@intel.com \
    --cc=ivdoorn@gmail.com \
    --cc=jbenc@suse.cz \
    --cc=jketreno@linux.intel.com \
    --cc=jkm@devicescape.com \
    --cc=johannes@sipsolutions.net \
    --cc=linville@tuxdriver.com \
    --cc=mbuesch@freenet.de \
    --cc=mcgrof@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon@devicescape.com \
    --cc=udayan.singh@gmail.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 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).