[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100203212641.GB30031@ZenIV.linux.org.uk>
Date: Wed, 3 Feb 2010 21:26:41 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Stephen Hemminger <shemminger@...tta.com>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [RFC] NAPI as kobject proposal
On Wed, Feb 03, 2010 at 09:23:36PM +0000, Ben Hutchings wrote:
> On Fri, 2010-01-29 at 10:18 -0800, Stephen Hemminger wrote:
> > The NAPI interface structure in current kernels is managed by the driver.
> > As part of receive packet steering there is a requirement to add an
> > additional parameter to this for the CPU map. And this map needs to
> > have an API to set it.
> >
> > The right way to do this in the kernel model is to make NAPI into
> > a kobject and associate it back with the network device (parent).
> > This isn't wildly difficult but does change some of the API for
> > network device drivers because:
> > 1. They need to handle another possible error on setup
> > 2. NAPI object needs to be dynamically allocated
> > separately (not as part of netdev_priv)
> > 3. Driver should pass index that can be uses as part of
> > name (easier than scanning)
4. Lifetime rules become oh-so-fscking-interesting?
--
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