netdev.vger.kernel.org archive mirror
 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 16:16:51 +0400	[thread overview]
Message-ID: <48D8DE33.6000605@bigtelecom.ru> (raw)
In-Reply-To: <20080923115708.GC4692@ff.dom.local>


> Actually, I don't use these things too much, but I guess, you'll need
> this more. Main issues were tested and fixed, but there could be always
> some details not used, not noticed or not reported until you decide to
> use this.
>   

Yep. I will begin test it in this week if i can get time for it...

> Yes, I'm not sure I understand question, but I think you shouldn't
> expect too much, at least in 2.6.27. There is many work now in drivers
> around this multiqueing (and RX hashing), which should be available in
> next kernels, but I'm not tracking this too much... Anyway, with the
> basic support (which really isn't common for drivers in 2.6.27 yet),
> this separation is done only for TX just before enqueuing.
>
>   
I simple hope that after divide to bands/queues and go back to network
all packets save "First in and First Out" logic that needed in services
like video streaming...

> 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).
>
>   
Ok! I will read all related information and rewrite all tc generate
scripts to test it!

> Don't worry, English should understand...
>
>   
Great what world have people that read messages like this and try
understand it... thanks!

> 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!!

not to worry ;) Thanks again. I try last -next git after someone fix
Intel exception issue ;)

  parent reply	other threads:[~2008-09-23 12:16 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
2008-09-23 12:16                         ` Badalian Vyacheslav [this message]
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=48D8DE33.6000605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).