All of lore.kernel.org
 help / color / mirror / Atom feed
From: Badalian Vyacheslav <slavon@bigtelecom.ru>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Machine Check Exception Re: NetDev! Please help!
Date: Tue, 23 Sep 2008 14:36:05 +0400	[thread overview]
Message-ID: <48D8C695.2020302@bigtelecom.ru> (raw)
In-Reply-To: <20080923092504.GB4692@ff.dom.local>


> 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.
>   
Very thanks for detailed information!
Yeh! Its sound great for me. I also can stress test this feature in our
network if you will needed it.

Only i have 2 question ...

1. If kernel use default situation (no tc user create rules, simple
autocreate by network card driver/module) its will normal work with
traffic what must delivered "as is" (not shape)... like IPTV or other
multicast/unicast video stream...
If i understand logic
we have 8 cpu/core and 4 TX queue and 4 RX... one cpu linked to 1
TX/RX.... but if 1 cpu is burned by some process - this cpu will send
its packet later when other cpu and packet is shape... but streams must
go packet by packet to receive device... I understand that it simple
need use hash function for TX queue, but if i understand - RX can't
separate packets to different queues (its doing by hardware?) by hash
function and packets may shape in rx stage because one CPU get it letter
when nedded?
I do not wish to spend your time... only say if it will work normal by
default and i will sleep easy :)

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?

Thanks and thanks again! And again sorry for my English.

Best regals, Badalyan Vyacheslav.

  reply	other threads:[~2008-09-23 10:36 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 [this message]
2008-09-23 11:57                       ` Jarek Poplawski
2008-09-23 12:06                         ` Jarek Poplawski
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=48D8C695.2020302@bigtelecom.ru \
    --to=slavon@bigtelecom.ru \
    --cc=jarkao2@gmail.com \
    --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.