From: Jeff Garzik <jeff@garzik.org>
To: Chris Snook <csnook@redhat.com>
Cc: atl1-devel@lists.sourceforge.net,
Jay Cliburn <jacliburn@bellsouth.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] atl1: Introduce CONFIG_ATL1_EXPERIMENTAL
Date: Fri, 07 Sep 2007 19:54:37 -0400 [thread overview]
Message-ID: <46E1E4BD.4000004@garzik.org> (raw)
In-Reply-To: <46E1E1AC.5030801@redhat.com>
Chris Snook wrote:
> The atl1 driver is currently marked EXPERIMENTAL, because a few
> supposedly performance-enhancing features still have problems. When
> these features are disabled, the driver is completely stable, fully
> functional, and performs well.
>
> Patch 1/2 Creates the kconfig option CONFIG_ATL1_EXPERIMENTAL, and
> removes the EXPERIMENTAL designation from CONFIG_ATL1
>
> Patch 2/2 Wraps some currently-disabled features in #ifdef
> CONFIG_ATL1_EXPERIMENTAL, so developers and testers can play with these
> features more easily, and distributions will still get a fast, stable
> driver with existing .config files.
>
> We'll also be using this to wrap around various new features we'll be
> experimenting with in coming months. Instead of using a half dozen
> different kconfig options for each of them, like some drivers do, we'll
> just use this, and make sure things are safe for everyone before we take
> them out of the experimental wrapper.
Well, I haven't received patch #2 yet, but in general a runtime switch
(module option?) is greatly preferred.
Jeff
next prev parent reply other threads:[~2007-09-07 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 23:41 [PATCH 0/2] atl1: Introduce CONFIG_ATL1_EXPERIMENTAL Chris Snook
2007-09-07 23:47 ` [PATCH 1/2] atl1: add CONFIG_ATL1_EXPERIMENTAL to kconfig Chris Snook
2007-09-07 23:52 ` [PATCH 2/2] atl1: wrap problematic optimizations in CONFIG_ATL1_EXPERIMENTAL Chris Snook
2007-09-08 0:21 ` [atl1-devel] " Luca
2007-09-08 0:27 ` Chris Snook
2007-09-07 23:54 ` Jeff Garzik [this message]
2007-09-08 0:06 ` [PATCH 0/2] atl1: Introduce CONFIG_ATL1_EXPERIMENTAL Chris Snook
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=46E1E4BD.4000004@garzik.org \
--to=jeff@garzik.org \
--cc=atl1-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=netdev@vger.kernel.org \
/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).