From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/14]: Make packet scheduler multiqueue aware.
Date: Tue, 15 Jul 2008 04:08:13 +0200 [thread overview]
Message-ID: <487C068D.3060002@trash.net> (raw)
In-Reply-To: <20080714.184849.121429019.davem@davemloft.net>
David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Tue, 15 Jul 2008 02:25:32 +0200
>
>
>> Unfortunately that seems to imply that anything but the really
>> simple qdiscs can't be used transparently in combination with
>> multiqueue without breaking configurations.
>>
>
> I think we can fix this after the merge window :)
>
Yes, that shouldn't be a problem.
>
> One idea is to allow all of the queues to point at a
> single qdisc. We'd just need to work out how to do the
> locking.
>
> For example, the Qdisc has a lock member, and a pointer.
> For simple qdiscs the pointer points at the netdev_queue
> lock. But when sharing, we use the in-Qdisc static lock
That sounds nice and easy.
next prev parent reply other threads:[~2008-07-15 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 22:59 [PATCH 0/14]: Make packet scheduler multiqueue aware David Miller
2008-07-15 0:25 ` Patrick McHardy
2008-07-15 1:48 ` David Miller
2008-07-15 2:08 ` Patrick McHardy [this message]
2008-07-16 4:14 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487C068D.3060002@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.