From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Michael Buesch <mbuesch@freenet.de>,
Jouni Malinen <jkmaline@cc.hut.fi>,
bcm43xx-dev@lists.berlios.de, linux-kernel@vger.kernel.org,
Feyd <feyd@seznam.cz>
Subject: Re: [Bcm43xx-dev] Broadcom 43xx first results
Date: Mon, 5 Dec 2005 19:20:06 +0000 [thread overview]
Message-ID: <20051205192006.GC28433@infradead.org> (raw)
In-Reply-To: <43948C65.4060405@pobox.com>
On Mon, Dec 05, 2005 at 01:52:21PM -0500, Jeff Garzik wrote:
> In general, Jouni's points are good, as are Michael's.
>
> The key question is about the size of the SoftMAC code. If its huge, an
> ieee80211 sub-module makes sense. If it's not, then adding the code to
> net/ieee80211 makes a lot more sense.
>
> Certainly some chips will use more ieee80211 code than others. This is
> no different than ethernet NICs: some make use of TSO and checksum
> offload code included in every kernel, while for other NICs the kernel
> TSO/csum code is just dead weight.
>
> In general, adding directly to net/ieee80211 is preferred, UNLESS there
> are overriding reasons not to do so (such as a huge size increase).
I tend to disagree a bit here. If it can be separate without making the
API more complicated a separate module is nicer, if the API would get nasty
integerating it is better. And nevermind whether it's a separate module or
not it should live in net/ieee80211/ ;-)
In either case ?I think this decision is better left until the code is in
an almost mergeable shape, because then the details will be clear.
next prev parent reply other threads:[~2005-12-05 19:20 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 18:50 Broadcom 43xx first results mbuesch
2005-12-04 19:52 ` [Bcm43xx-dev] " Feyd
2005-12-04 19:58 ` Michael Buesch
2005-12-05 5:50 ` Jouni Malinen
2005-12-05 6:05 ` Benjamin Herrenschmidt
2005-12-05 11:08 ` Michael Buesch
2005-12-05 14:19 ` Jouni Malinen
2005-12-05 14:28 ` Michael Buesch
2005-12-05 14:41 ` Jouni Malinen
2005-12-05 18:52 ` Jeff Garzik
2005-12-05 19:20 ` Christoph Hellwig [this message]
2005-12-05 18:00 ` Jiri Benc
2005-12-05 18:14 ` Michael Renzmann
2005-12-05 18:24 ` Stephen Hemminger
2005-12-05 18:46 ` Jeff Garzik
2005-12-05 18:49 ` Jiri Benc
2005-12-05 18:54 ` Jeff Garzik
2005-12-05 19:11 ` Jiri Benc
2005-12-30 10:34 ` Rakotomandimby Mihamina
2005-12-06 7:17 ` Michael Renzmann
2005-12-05 18:38 ` Joseph Jezak
2005-12-05 18:55 ` Jiri Benc
2005-12-05 19:08 ` Jeff Garzik
2005-12-05 19:18 ` Jiri Benc
2005-12-05 19:53 ` Dave Jones
2005-12-05 20:09 ` Jeff Garzik
2005-12-06 15:10 ` Harald Welte
2005-12-06 19:05 ` Jeff Garzik
2005-12-06 20:53 ` Stephen Hemminger
2005-12-07 7:16 ` Harald Welte
2005-12-06 23:19 ` David S. Miller
2005-12-06 23:45 ` Jeff Garzik
2005-12-07 13:34 ` Michael Buesch
2005-12-08 11:32 ` Jiri Benc
2005-12-08 12:07 ` Jiri Benc
2005-12-08 12:12 ` Arjan van de Ven
2005-12-08 13:03 ` Jiri Benc
2005-12-05 19:10 ` Christoph Hellwig
2005-12-05 19:31 ` Jiri Benc
2005-12-05 19:41 ` Christoph Hellwig
2005-12-05 20:11 ` Jiri Benc
2005-12-06 15:09 ` Pavel Machek
2005-12-06 16:43 ` Ben Greear
2005-12-06 23:25 ` David S. Miller
2005-12-06 19:24 ` Jeff Garzik
2005-12-06 15:04 ` Pavel Machek
2005-12-08 0:00 ` Michael Wu
2005-12-08 1:05 ` Jeff Garzik
2005-12-05 20:23 ` Michael Buesch
2005-12-05 20:42 ` Jiri Benc
2005-12-06 9:26 ` Kyle Moffett
2005-12-06 10:23 ` Luc Saillard
2005-12-05 19:40 ` Pavel Machek
2005-12-05 20:14 ` Michael Buesch
2005-12-05 20:35 ` Pavel Machek
2005-12-05 20:40 ` Arjan van de Ven
2005-12-05 20:40 ` Michael Buesch
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=20051205192006.GC28433@infradead.org \
--to=hch@infradead.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=feyd@seznam.cz \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
/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