All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Badalian Vyacheslav <slavon@bigtelecom.ru>
Cc: netdev@vger.kernel.org
Subject: Re: Machine Check Exception Re: NetDev! Please help!
Date: Tue, 23 Sep 2008 12:06:44 +0000	[thread overview]
Message-ID: <20080923120644.GD4692@ff.dom.local> (raw)
In-Reply-To: <20080923115708.GC4692@ff.dom.local>

On Tue, Sep 23, 2008 at 11:57:08AM +0000, Jarek Poplawski wrote:
> On Tue, Sep 23, 2008 at 02:36:05PM +0400, Badalian Vyacheslav wrote:
> > 
> > > 2) Non-default qdiscs (any qdiscs added with tc): there is only one
> > > root qdisc (with its tree) as before, dequeued to all tx queues (if
> > > available). Since there is only one qdisc lock, and additional flag
> > > preventing other processes to run the qdisc at the same time, there
> > > is not so much advantage of SMP, except on tx locking. All previous
> > > tc configs should work without changes (except sch_prio and sch_rr
> > > used for multiqueuing, replaced by sch_multiq and act_skbedit now).
> > > Probably in some cases adding sch_multiq to a tree for separating
> > > qdisc queues per tx queues could be useful.
...
> > 2. I can locate module like sch_multiq at last 2.6.27-rc tree and not
> > have information of it in google... I need to know only one thing - what
> > params for hashing was planned for it?
> 
> sch_multiq doesn't use any params for hashing now - it uses mapping
> in packets to separate them to different bands/queues. So, by default
> it'll respect common hashing. You can change this using any filter with
> act_skbedit (Documentation/networking/multiqueue.txt).

OOPS!!! This 2.6.27-rc is so ...old I forgot the sch_multiq and
act_skbedit are only for the -next!

I'm very sorry for misleading!!!
Jarek P.

  reply	other threads:[~2008-09-23 12:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-20 13:19 NetDev! Please help! Badalian Vyacheslav
2008-09-20 13:38 ` Badalian Vyacheslav
2008-09-20 18:11 ` Denys Fedoryshchenko
2008-09-21 16:11   ` Jarek Poplawski
     [not found]     ` <48D7385D.40107@bigtelecom.ru>
2008-09-22  6:53       ` Machine Check Exception " Jarek Poplawski
2008-09-22  8:05         ` Jarek Poplawski
2008-09-22  9:40         ` Badalian Vyacheslav
2008-09-22 11:24           ` Jarek Poplawski
2008-09-22 13:00             ` Badalian Vyacheslav
2008-09-22 17:23               ` Jarek Poplawski
2008-09-23  7:43                 ` Badalian Vyacheslav
2008-09-23  9:25                   ` Jarek Poplawski
2008-09-23 10:36                     ` Badalian Vyacheslav
2008-09-23 11:57                       ` Jarek Poplawski
2008-09-23 12:06                         ` Jarek Poplawski [this message]
2008-09-23 12:16                         ` Badalian Vyacheslav
2008-09-23 18:26                           ` Jarek Poplawski
2008-09-20 18:31 ` Machine Check Exception Was: " Jarek Poplawski

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=20080923120644.GD4692@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=slavon@bigtelecom.ru \
    /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.