From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: [PATCH 0/3] e100: Enable receiving bogus packets and saving FCS
Date: Tue, 25 Nov 2003 01:17:28 -0800 [thread overview]
Message-ID: <3FC31E28.8060106@candelatech.com> (raw)
David S. Miller wrote:
> On Mon, 24 Nov 2003 15:48:25 -0800
> Ben Greear <greearb@candelatech.com> wrote:
>
>
>>So, RX-ALL can be one flag, another for RX-FCS, and the TX-CUSTOM-FCS
>>can be a separate patch altogether?
>
>
> That is the basic idea, yes.
Here are three patches. These were extracted manually from my
big patchset. Where flags are defined, I left in the pktgen receive
flag and the send-to-self flag from my larger patch set.
If this is unacceptable, I can shuffle the flags around....
rx_all_ethtool.patch is the ethtool glue to turn on/off the RX-ALL and SAVE-FCS
flags. I have not tested any of the ethtool-ops code branches as e100 and e1000
does not appear to use it.
rx_all_headers.patch should take care of defining the flags in if.h and netdevice.h
rx_all_e100.patch converts the e100 driver to support these features. I've
ripped out the tx-custom-fcs code, but the rx-all and save-fcs code is there.
The default behaviour is virtually identical, because while the old code
was enabling receiving a lot of bad packets when in PROMISC mode, the check
in e100_main rx code was throwing away anything that was not marked as good
anyway...
> However, one thing I want to make absolutely clear is that I do not
> want multiple ways to get the same information out of the kernel.
> We decided to build netlink into the kernel always because this means
> it is present in everyone's kernel. And therefore, we don't need to
> add another way to obtain the same config information already
> available via netlink. The existing cases where an ioctl() style
> call exists to obtain the same info available via netlink is merely
> for compatability with older BSD tools. No new such things will be
> added.
Ok, I won't ask again. I attempted to get rid of all the 'ndstats'
code from these patches. If some is still in there, it's an accident
and I'll remove it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2003-11-25 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 9:17 Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 23:24 [PATCH] e100: Enable receiving bogus packets, and transmitting bad/custom CRC Ben Greear
2003-11-24 23:29 ` David S. Miller
2003-11-24 23:48 ` Ben Greear
2003-11-25 1:33 ` David S. Miller
2003-11-25 7:53 ` [PATCH 0/3] e100: Enable receiving bogus packets and saving FCS Ben Greear
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=3FC31E28.8060106@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.