netdev - RE: [PATCH 0/2] NET: Multiple queue network device support REPOST

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <D5C1322C3E673F459512FB59E0DDC329026E982F@orsmsx414.amr.corp.intel.com>
Date:	Thu, 8 Mar 2007 23:16:58 -0800
From:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	"Leech, Christopher" <christopher.leech@...el.com>
Subject: RE: [PATCH 0/2] NET: Multiple queue network device support REPOST

> This is not a problem.
> 
> Since the ->enqueue function stores references to the SKBs, 
> any change of the dev->qdisc has to flush those references 
> somehow, and it is at that point that you can fixup the skb 
> queue mappings.
> 
> This happens via invoking the qdisc->ops->reset() method.
> 

Thanks Dave.  It seems expensive to change all the skb's if this type of
event occurs, but I suppose it is a corner case and can be tolerated.
Please let me make this change and I'll resubmit.

Also, the first patch set was RFC, and you were the only one to submit
feedback to me.  :-/  So I figured submitting as an official patch for
feedback might get more attention.

And to reiterate what Auke asked, what did happen to the patches?  I see
things getting through the netdev mailing list, but they're not showing
up on www.spinics.net/lists/netdev.  Was it something I did when
sending, or did majordomo hiccup?

Thanks,

-PJ Waskiewicz
-
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