From: jamal <hadi@cyberus•ca>
To: Changli Gao <xiaosuo@gmail•com>
Cc: Eric Dumazet <eric.dumazet@gmail•com>,
"David S. Miller" <davem@davemloft•net>,
Tom Herbert <therbert@google•com>,
Linux Netdev List <netdev@vger•kernel.org>
Subject: Re: [RFC] act_cpu: redirect skb receiving to a special CPU.
Date: Sat, 05 Jun 2010 09:07:04 -0400 [thread overview]
Message-ID: <1275743224.3490.44.camel@bigi> (raw)
In-Reply-To: <AANLkTikskTWJrULj2IKYhebxh9O_XTOMBy3i0wPY8thq@mail.gmail.com>
Changli,
I like the idea..
My preference would be to not change ingress qdisc to have queues.
The cpuid should be sufficient to map to a remote cpu queue, no?
Now, if you could represent each cpu as a netdevice, then we wouldnt
need any change;-> And we could have multiple types of ways to redirect
to cpus instead of just doing IPIs - example, ive always thought of
sending over something like HT (I think it would be a lot cheaper).
I didnt queit understand the map OFFSET part. is this part of rfs?
cheers,
jamal
On Sat, 2010-06-05 at 18:56 +0800, Changli Gao wrote:
> I am going to implement a CPU action, which can be used with ingress
> qdisc to redirect skb receiving to a special cpu. It is much like RPS,
> but more flexible:
>
> * choose the hash function with the help of cls_flow.c
> * pin special traffic to a dedicate CPU
> * weighted packets distributing
>
> act_cpu will use the function enqueue_to_backlog() supplied by RPS to
> redirect skb receiving, and have two kind paramter:
>
> * cpu CPUID - the ID of CPU, which handles this traffic
> * map OFFSET - map the mirror class ID to CPUID: CPUID = mirror class ID + CPUID
>
> sch_ingress will be enhanced to support class tree.
>
next prev parent reply other threads:[~2010-06-05 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 10:56 [RFC] act_cpu: redirect skb receiving to a special CPU Changli Gao
2010-06-05 13:07 ` jamal [this message]
2010-06-05 13:26 ` Changli Gao
2010-06-05 13:54 ` jamal
2010-06-05 14:15 ` Changli Gao
2010-06-05 14:26 ` jamal
2010-06-05 15:00 ` Eric Dumazet
2010-06-07 8:43 ` Andi Kleen
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=1275743224.3490.44.camel@bigi \
--to=hadi@cyberus$(echo .)ca \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=therbert@google$(echo .)com \
--cc=xiaosuo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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