From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarek Poplawski Subject: Re: [PATCH 1/2] NET: Multiple queue network device support Date: Mon, 12 Mar 2007 09:58:02 +0100 Message-ID: <20070312085802.GA1664@ff.dom.local> References: <20070309134037.GH521@postel.suug.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Kok\, Auke" , David Miller , "Garzik\, Jeff" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Peter Waskiewicz Jr , "Brandeburg\, Jesse" , "Kok\, Auke" , "Ronciak\, John" To: Thomas Graf Return-path: Received: from mx10.go2.pl ([193.17.41.74]:35373 "EHLO poczta.o2.pl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S965352AbXCLIxx (ORCPT ); Mon, 12 Mar 2007 04:53:53 -0400 Content-Disposition: inline In-Reply-To: <20070309134037.GH521@postel.suug.ch> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 09-03-2007 14:40, Thomas Graf wrote: > * Kok, Auke 2007-02-08 16:09 >> diff --git a/net/core/dev.c b/net/core/dev.c >> index 455d589..42b635c 100644 >> --- a/net/core/dev.c >> +++ b/net/core/dev.c >> @@ -1477,6 +1477,49 @@ gso: >> skb->tc_verd = SET_TC_AT(skb->tc_verd,AT_EGRESS); >> #endif >> if (q->enqueue) { >> +#ifdef CONFIG_NET_MULTI_QUEUE_DEVICE >> + int queue_index; >> + /* If we're a multi-queue device, get a queue index to lock */ >> + if (netif_is_multiqueue(dev)) >> + { >> + /* Get the queue index and lock it. */ >> + if (likely(q->ops->map_queue)) { >> + queue_index = q->ops->map_queue(skb, q); >> + spin_lock(&dev->egress_subqueue[queue_index].queue_lock); >> + rc = q->enqueue(skb, q); I'm not sure Dave Miller thought about this place, when he proposed to save the mapping, but I think this could be not enough. This place is racy: ->map_queue() is called 2 times and with some filters (and policies/actions) results could differ. And of course the subqueue lock doesn't prevent any filter from a config change in the meantime. After second reading of this patch I have doubts it's the proper way to solve the problem: there are many subqueues but we need a top queue (prio here) to mange them, anyway. So, why not to build this functionality directly into the queue? There is no difference for a device if skbs are going from the subqueue or a class, it is only interested in the mapping result and a possibility to stop and start a subqueue and to query its status. All this could be done by adding the callbacks directly to any classful scheduler or, if not enough, to write some specialized qdisc based on prio. The possibility to lock only a subqueue instead of a queue could be analized independently - current proposal doesn't solve this anyway. Regards, Jarek P.