From: Eric Dumazet <eric.dumazet@gmail.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Eliezer Tamir <eliezer.tamir@linux.intel.com>,
Shawn Bohrer <sbohrer@rgmadvisors.com>,
Amir Vadai <amirv@mellanox.com>,
netdev@vger.kernel.org, "Kirsher,
Jeffrey T" <jeffrey.t.kirsher@intel.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
John Fastabend <john.r.fastabend@intel.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>
Subject: Re: low latency/busy poll feedback and bugs
Date: Tue, 06 Aug 2013 14:02:58 -0700 [thread overview]
Message-ID: <1375822978.4004.12.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAJZOPZKByh7LzH0w25dDG_5jOvg7wPrmiVcMJ0xBhOJxaE0Zcw@mail.gmail.com>
On Tue, 2013-08-06 at 23:39 +0300, Or Gerlitz wrote:
> On Tue, Aug 6, 2013 at 10:41 AM, Eliezer Tamir
> <eliezer.tamir@linux.intel.com> wrote:
> > On 06/08/2013 00:22, Shawn Bohrer wrote:
> >> 1) I'm testing with a Mellanox ConnectX-3 card.
> >
> > There's your problem ;)
>
> Can you be more specific? I love testing with Intel Niantic, do code
> inspetion of the ixgbe driver and interact with Jeff/Greg/Alex/John
> and all the other great folks from the Intel Linux networking team,
> actually that (happily working with your competitors) is crucial part
> of the fun in open source / upstream work. What's wrong with using
> NICs which don't have intel.com on their paper cover?
I don't think there is something wrong.
Eliezer tone was quite clear ;)
BTW, I do not have a Niantic cards to play with, Intel guys feel free to
send me samples ;)
Thanks
next prev parent reply other threads:[~2013-08-06 21:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 21:22 low latency/busy poll feedback and bugs Shawn Bohrer
2013-08-05 22:16 ` [PATCH net-next] net: Add low-latency/polling support for UDP multicast Shawn Bohrer
2013-08-06 7:13 ` Eliezer Tamir
2013-08-06 19:51 ` [PATCH v2 " Shawn Bohrer
2013-08-07 20:22 ` Eric Dumazet
2013-08-08 8:46 ` Eliezer Tamir
2013-08-08 23:55 ` Eric Dumazet
2013-08-11 7:59 ` Eliezer Tamir
2013-08-06 7:41 ` low latency/busy poll feedback and bugs Eliezer Tamir
2013-08-06 18:08 ` Shawn Bohrer
2013-08-06 18:25 ` Eliezer Tamir
2013-08-07 20:05 ` Ben Hutchings
2013-08-07 20:23 ` Eric Dumazet
2013-08-07 23:41 ` David Miller
2013-08-06 20:39 ` Or Gerlitz
2013-08-06 21:02 ` Eric Dumazet [this message]
2013-08-06 12:15 ` Amir Vadai
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=1375822978.4004.12.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=amirv@mellanox.com \
--cc=eliezer.tamir@linux.intel.com \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=sbohrer@rgmadvisors.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;
as well as URLs for NNTP newsgroup(s).