[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100426.132435.245397555.davem@davemloft.net>
Date: Mon, 26 Apr 2010 13:24:35 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: scofeldm@...co.com
Cc: netdev@...r.kernel.org, chrisw@...hat.com, arnd@...db.de
Subject: Re: [net-next-2.6 PATCH 1/2] Add ndo_set_vf_port_profile
From: Scott Feldman <scofeldm@...co.com>
Date: Mon, 26 Apr 2010 12:27:51 -0700
> We'd need an array of struct ifla_vf_port_profile hanging off of netdev, one
> element for each VF. That seems like a lot of mem hanging off of netdev,
> and we'd have to define a MAX_VF to size the array. How about a
> ndo_get_vf_port_profile() that the netdev fills in, and the netdev keeps the
> data in it's private area? That's how ndo_get_vf_config() is working.
Sure if the device can do it, but for situations where it can't we can
use a linked list and dynamic memory allocation.
--
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