From: Eric Dumazet <eric.dumazet@gmail.com>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
John Fastabend <john.r.fastabend@intel.com>,
Xinan Tang <xinan.tang@intel.com>,
Junchang Wang <junchangwang@gmail.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] Kernel interfaces for multiqueue aware socket
Date: Wed, 15 Dec 2010 21:56:07 +0100 [thread overview]
Message-ID: <1292446567.2603.15.camel@edumazet-laptop> (raw)
In-Reply-To: <1292446118.2603.11.camel@edumazet-laptop>
Le mercredi 15 décembre 2010 à 21:48 +0100, Eric Dumazet a écrit :
> Le mercredi 15 décembre 2010 à 12:02 -0800, Fenghua Yu a écrit :
> > From: Fenghua Yu <fenghua.yu@intel.com>
> >
> > Multiqueue and multicore provide packet parallel processing methodology.
> > Current kernel and network drivers place one queue on one core. But the higher
> > level socket doesn't know multiqueue. Current socket only can receive or send
> > packets through one network interfaces. In some cases e.g. multi bpf filter
> > tcpdump and snort, a lot of contentions come from socket operations like ring
> > buffer. Even if the application itself has been fully parallelized and run on
> > multi-core systems and NIC handlex tx/rx in multiqueue in parallel, network layer
> > and NIC device driver assemble packets to a single, serialized queue. Thus the
> > application cannot actually run in parallel in high speed.
I forgot to say that your patches are not against net-next-2.6, and not
apply anyway.
Always use David trees for networking patches...
next prev parent reply other threads:[~2010-12-15 20:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 20:02 [PATCH 0/3] Kernel interfaces for multiqueue aware socket Fenghua Yu
2010-12-15 20:02 ` [PATCH 1/3] " Fenghua Yu
2010-12-15 20:48 ` Eric Dumazet
2010-12-15 20:56 ` Eric Dumazet [this message]
2010-12-16 1:14 ` Fenghua Yu
2010-12-16 1:23 ` Stephen Hemminger
2010-12-16 1:28 ` Changli Gao
2010-12-16 2:43 ` Dimitris Michailidis
2010-12-17 6:22 ` Junchang Wang
2010-12-17 6:50 ` Eric Dumazet
2010-12-16 4:44 ` Eric Dumazet
2010-12-17 6:12 ` Junchang Wang
2010-12-16 1:52 ` Junchang Wang
2010-12-16 5:00 ` Eric Dumazet
2010-12-17 6:15 ` Junchang Wang
2010-12-15 20:52 ` John Fastabend
2010-12-15 20:02 ` [PATCH 2/3] net/packet/af_packet.c: implement multiqueue aware socket in af_apcket Fenghua Yu
2010-12-15 20:02 ` [PATCH 3/3] drivers/net/ixgbe/ixgbe_main.c: get tx queue mapping specified in socket Fenghua Yu
2010-12-15 20:54 ` John Fastabend
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=1292446567.2603.15.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=fenghua.yu@intel.com \
--cc=john.r.fastabend@intel.com \
--cc=junchangwang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xinan.tang@intel.com \
/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