From: Chris Snook <csnook@redhat.com>
To: "J. K. Cliburn" <jcliburn@gmail.com>
Cc: jeff@garzik.org, Jie.yang@atheros.com, netdev@vger.kernel.org
Subject: Re: atl1: use magic packet wake-on-lan only
Date: Wed, 12 Nov 2008 12:37:00 -0500 [thread overview]
Message-ID: <491B143C.5050404@redhat.com> (raw)
In-Reply-To: <20081111183546.72de1714@osprey.hogchain.net>
J. K. Cliburn wrote:
> On Mon, 10 Nov 2008 13:42:25 -0500
> Chris Snook <csnook@redhat.com> wrote:
>
>> J. K. Cliburn wrote:
>>> atl1: use magic packet wake-on-lan only
>>>
>>> Of the various WOL options provided in include/linux/ethtool.h, the
>>> L1 NIC supports only magic packet. Remove all options except magic
>>> packet from the atl1 driver.
>> Technically, we could implement the rest via the programmable
>> pattern-matching hardware, but that would be an immense amount of
>> work.
>
> Thanks for the pointer to the pattern matching capability. I had
> forgotten about it.
>
> What prompted the patch was a user asking some questions off-list about
> the L1 and WOL, and I realized the atl1 driver was advertising WOL
> options that weren't implemented.
>
> I think the magic-packet-only patch I submitted to Jeff is still
> relevant, but I'm going to explore the pattern matching capability and
> see if we can implement some additional WOL options. IMHO, though,
> those should be provided in a separate (future) patch. Do you agree?
>
> Jay
Completely. Programming the pattern matching hardware is a lot more
involved than setting a single bit in the hardware.
Are there any other NICs that have pattern-matching WoLAN capability?
If so, how do their drivers take advantage of them? If it turns out to
be a widely underutilized feature, it might make sense to let ethtool do
the dirty work.
-- Chris
prev parent reply other threads:[~2008-11-12 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 21:05 atl1: use magic packet wake-on-lan only J. K. Cliburn
2008-11-10 18:42 ` Chris Snook
2008-11-12 0:35 ` J. K. Cliburn
2008-11-12 17:37 ` Chris Snook [this message]
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=491B143C.5050404@redhat.com \
--to=csnook@redhat.com \
--cc=Jie.yang@atheros.com \
--cc=jcliburn@gmail.com \
--cc=jeff@garzik.org \
--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).