From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Nick Kossifidis" <mickflemm@gmail.com>,
"Stefanik Gábor" <netrolller.3d@gmail.com>,
"Glenn Burkhardt" <gbburkhardt@verizon.net>,
"Bob Copeland" <me@bobcopeland.com>,
linux-wireless@vger.kernel.org
Subject: Re: poor performance with ath5k; reverting to ath_pci
Date: Thu, 22 Jan 2009 09:17:35 -0500 [thread overview]
Message-ID: <20090122141734.GA3646@tuxdriver.com> (raw)
In-Reply-To: <1232633075.4224.6.camel@johannes.local>
On Thu, Jan 22, 2009 at 03:04:35PM +0100, Johannes Berg wrote:
> On Thu, 2009-01-22 at 08:49 -0500, John W. Linville wrote:
> > On Thu, Jan 22, 2009 at 06:32:55AM +0200, Nick Kossifidis wrote:
> > > 2009/1/21 Stefanik G=E1bor <netrolller.3d@gmail.com>:
> > > >
> > > > I think EMBEDDED is for options that replace full-featured Linu=
x
> > > > components with dumbed-down, "low-profile" equivalents (like SL=
OB) -
> > > > PID vs. minstrel is more like SLAB vs. SLUB.
> > > >
> > > > G=E1bor
> > > >
> > >=20
> > > Minstrell performs very well even on embedded devices, i don't th=
ink
> > > it's that heavy compared to pid.
> >=20
> > I think his point was that people should be able to select multiple
> > algorithms without having to select EMBEDDED.
>=20
> The reason it was originally under EMBEDDED is that this allows you t=
o
> turn off _all_ algorithms, and that breaks, but might be desirable if
> you have a system where you know you're using iwlagn or ath9k only wh=
ich
> have their own algorithms.
I see. But currently it limits you to only one generic algorithm, the
one chosen as the default. I don't think that was really the intent?
John
--=20
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-22 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 5:03 poor performance with ath5k; reverting to ath_pci Glenn Burkhardt
2009-01-14 13:30 ` Nick Kossifidis
2009-01-15 22:34 ` Glenn Burkhardt
2009-01-16 15:33 ` Bob Copeland
2009-01-21 3:38 ` Glenn Burkhardt
2009-01-21 15:14 ` John W. Linville
2009-01-21 18:22 ` Stefanik Gábor
2009-01-21 19:11 ` John W. Linville
2009-01-21 19:33 ` Stefanik Gábor
2009-01-21 19:34 ` John W. Linville
2009-01-22 4:32 ` Nick Kossifidis
2009-01-22 13:49 ` John W. Linville
2009-01-22 14:04 ` Johannes Berg
2009-01-22 14:17 ` John W. Linville [this message]
2009-01-22 14:45 ` Stefanik Gábor
2009-01-22 15:18 ` John W. Linville
2009-01-22 2:58 ` Glenn Burkhardt
2009-01-23 7:31 ` Nick Kossifidis
2009-02-03 2:36 ` Glenn Burkhardt
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=20090122141734.GA3646@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=gbburkhardt@verizon.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=netrolller.3d@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).