[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20131007.173433.163556658910279518.davem@davemloft.net>
Date: Mon, 07 Oct 2013 17:34:33 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nhorman@...driver.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] net: Add layer 2 hardware acceleration operations
for macvlan devices
From: Neil Horman <nhorman@...driver.com>
Date: Mon, 7 Oct 2013 17:20:00 -0400
> Thats me experimenting. I was thinking that origionally this functionality
> might be grouped separately, so that we could handle it independently of the
> standard network device operations (you might have noticed in v1 of my patch I
> had a size_t variable in there, so I thought the separation might be
> organizationally nice). It was also something I was tinkering with for
> potential future work to support other data plane accelerators (like the FM6000
> switch chip from intel) in a manner that didn't pollute the more typical host network
> devices. Like I said though, just experimenting at the moment....
Can these dataplane devices still act like a normal networking port and
send and receive packets at the host level?
If yes, that would be an extremely strong argument for netdev_ops.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists