From: Stephen Hemminger <shemminger@osdl.org>
To: Alex Aizman <alex@neterion.com>
Cc: netdev@vger.kernel.org
Subject: Re: VJ Channel API - driver level (PATCH)
Date: Tue, 2 May 2006 16:00:58 -0700 [thread overview]
Message-ID: <20060502160058.7af02254@localhost.localdomain> (raw)
In-Reply-To: <4457E2FE.50505@neterion.com>
On Tue, 02 May 2006 15:53:50 -0700
Alex Aizman <alex@neterion.com> wrote:
> Signed-off-by: Alex Aizman <alex@xxxxxxxxxx>
>
> Hacked netdevice.h to support multiple channels.
>
> --- netdevice-orig.h 2006-03-04 10:01:38.000000000 -0800
> +++ netdevice-channel.h 2006-03-09 10:17:11.419955200 -0800
> @@ -246,6 +246,147 @@
>
> extern int __init netdev_boot_setup(char *str);
>
> +#ifdef CONFIG_NET_CHANNELS
> +/*************** NETDEVICE HW CHANNELS data structures *****************/
> +/**
> + * enum netdev_hwchannel_rx_flow_e - Hardware receive channel "flow" types.
> + * @HWCH_RX_FLOW_NONE: does not filter rx packets.
> + * @HWCH_RX_FLOW_MACADDR: filters based upon the rx mac address
> + * @HWCH_RX_FLOW_VLAN_ID: filters based upon the rx vlan id tag
> + * @HWCH_RX_FLOW_VLAN_QOS: fikters based upon the vlan qos field
> + * @HWCH_RX_FLOW_PORT: filters based upon the tcp or udp receive port number
> + * @HWCH_RX_FLOW_L4_HASH: filters based upon a hash of the tcp session id
> + * @HWCH_RX_FLOW_L4_SPDM: filters based upon a hash of the four-tuple of the
> + * following: source ip, source port, destination ip, destinaton port
> + *
> + * A rx is bound to a specific device. When one of thsese enums is used,
> + * traffic is filtered onto the queue of only the requested type. By default
> + * we use HWCH_RX_FLOW_NONE as we usually want all traffic from this device.
> + **/
> +typedef enum netdev_hwchannel_rx_flow_e {
> + HWCH_RX_FLOW_NONE,
> + HWCH_RX_FLOW_MACADDR,
> + HWCH_RX_FLOW_VLAN_ID,
> + HWCH_RX_FLOW_VLAN_QOS,
> + HWCH_RX_FLOW_PORT,
> + HWCH_RX_FLOW_L4_HASH,
> + HWCH_RX_FLOW_L4_SPDM,
> +} netdev_hwchan_rx_flow_e;
> +
No, not a typedef. also pls use shorter names.
next prev parent reply other threads:[~2006-05-02 23:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 22:53 VJ Channel API - driver level (PATCH) Alex Aizman
2006-05-02 23:00 ` Stephen Hemminger [this message]
2006-05-03 6:47 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 13:56 Leonid Grossman
2006-05-03 20:23 ` David S. Miller
2006-05-03 15:56 Caitlin Bestler
2006-05-03 18:07 ` Evgeniy Polyakov
2006-05-03 18:45 ` YOSHIFUJI Hideaki / 吉藤英明
2006-05-03 20:35 ` David S. Miller
2006-05-03 17:52 Caitlin Bestler
2006-05-03 18:12 Caitlin Bestler
2006-05-03 18:49 ` Stephen Hemminger
2006-05-03 20:40 Caitlin Bestler
2006-05-04 22:49 ` Alex Aizman
2006-05-04 23:04 ` David S. Miller
2006-05-05 9:36 ` Evgeniy Polyakov
2006-05-06 0:35 ` David S. Miller
2006-05-06 8:42 ` Evgeniy Polyakov
2006-05-06 8:57 ` Evgeniy Polyakov
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=20060502160058.7af02254@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=alex@neterion.com \
--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 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.