lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b0438a630902230121l5f0d3af4id9f98b877869e192@mail.gmail.com>
Date:	Mon, 23 Feb 2009 10:21:15 +0100
From:	Miguel Ángel Álvarez <gotzoncabanes@...il.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: NAPI of many interfaces with just an interruption source

Thanks for the help

On Sat, Feb 21, 2009 at 10:19 PM, Benjamin Herrenschmidt
<benh@...nel.crashing.org> wrote:
>
>> Ben has just done exactly the same thing for his driver so he
>> can tell you all about it and how to use his generic function :)
>
> Right, you can look how it's done in ibm_newemac. There's basically
> a "dummy" netdev which is created to handle the NAPI on behalf of
> the real ones. The new core function init_dummy_netdev() will set
> up that dummy netdev for you.
>
I am working with 2.26.7... I do not have that "init_dummy_netdev" for
what I see.

> If you look at how I do it in emac, the actual ports "register"
> internally with that "mal" module so that I can "poll" them when
> the main NAPI is polled.
>
I see how it works... Nice. So it seems there is API to work with NAPI
"out of" net interfaces. Perhaps that is what I need.

Just a question... Why do you register the dummy "mal" as a driver?
Should it not be enough to init it when the first real driver is
loaded?

Miguel Ángel
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ