All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Eliezer Tamir <eliezer.tamir@linux.jf.intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Dave Miller <davem@davemloft.net>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	e1000-devel@lists.sourceforge.net,
	Willem de Bruijn <willemb@google.com>,
	Andi Kleen <andi@firstfloor.org>, HPA <hpa@zytor.com>,
	Eliezer Tamir <eliezer@tamir.org.il>
Subject: Re: [RFC PATCH 0/5] net: low latency Ethernet device polling
Date: Mon, 04 Mar 2013 15:37:56 +0800	[thread overview]
Message-ID: <51344F54.8060809@gmail.com> (raw)
In-Reply-To: <20130227175549.10611.82188.stgit@gitlad.jf.intel.com>

On 02/28/2013 01:55 AM, Eliezer Tamir wrote:
>
> Open issues:
> 1. Find a way to avoid the need to change the sk and skb structs.
> One big disadvantage of how we do this right now is that when a device is
> removed, it's hard to prevent it from getting polled by a socket
> which holds a stale reference.
>
> 2. How do we decide which sockets are eligible to do busy polling?
> Do we add a socket option to control this?
> How do we provide sane defaults while allowing flexibility and performance?
>
> 3. Andi Kleen and HPA pointed out that using get_cycles() is not portable.
>
> 4. How and where do we call ndo_ll_poll from the socket code?
> One good place seems to be wherever the kernel puts the process to sleep,
> waiting for more data, but this makes doing something intelligent about
> poll (the system call) hard. From the perspective of how ndo_ll_poll
> itself is implemented this does not seem to matter.
>
> 5. I would like to hear suggestions on naming conventions and where
> to put the code that for now I have put in include/net/ll_poll.h
>


A dumb question: is bypassing tcpdump/netfilters/qdisc etc. what we 
always want? Isn't this a security issue?

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Eliezer Tamir <eliezer.tamir@linux.jf.intel.com>
Cc: Willem de Bruijn <willemb@google.com>,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	HPA <hpa@zytor.com>, Eliezer Tamir <eliezer@tamir.org.il>,
	Dave Miller <davem@davemloft.net>
Subject: Re: [RFC PATCH 0/5] net: low latency Ethernet device polling
Date: Mon, 04 Mar 2013 15:37:56 +0800	[thread overview]
Message-ID: <51344F54.8060809@gmail.com> (raw)
In-Reply-To: <20130227175549.10611.82188.stgit@gitlad.jf.intel.com>

On 02/28/2013 01:55 AM, Eliezer Tamir wrote:
>
> Open issues:
> 1. Find a way to avoid the need to change the sk and skb structs.
> One big disadvantage of how we do this right now is that when a device is
> removed, it's hard to prevent it from getting polled by a socket
> which holds a stale reference.
>
> 2. How do we decide which sockets are eligible to do busy polling?
> Do we add a socket option to control this?
> How do we provide sane defaults while allowing flexibility and performance?
>
> 3. Andi Kleen and HPA pointed out that using get_cycles() is not portable.
>
> 4. How and where do we call ndo_ll_poll from the socket code?
> One good place seems to be wherever the kernel puts the process to sleep,
> waiting for more data, but this makes doing something intelligent about
> poll (the system call) hard. From the perspective of how ndo_ll_poll
> itself is implemented this does not seem to matter.
>
> 5. I would like to hear suggestions on naming conventions and where
> to put the code that for now I have put in include/net/ll_poll.h
>


A dumb question: is bypassing tcpdump/netfilters/qdisc etc. what we 
always want? Isn't this a security issue?

Thanks!

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

  parent reply	other threads:[~2013-03-04  7:38 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 17:55 [RFC PATCH 0/5] net: low latency Ethernet device polling Eliezer Tamir
2013-02-27 17:55 ` [RFC PATCH 1/5] net: implement support for low latency socket polling Eliezer Tamir
2013-03-03 18:35   ` Eric Dumazet
2013-03-03 19:21     ` Andi Kleen
2013-03-03 21:20       ` Eric Dumazet
2013-03-04  3:55         ` Andi Kleen
2013-03-04  8:43     ` Eliezer Tamir
2013-03-04 14:52       ` Eric Dumazet
2013-03-04 15:28         ` Eliezer Tamir
2013-03-04 16:15           ` Eric Dumazet
2013-03-04  7:23   ` Cong Wang
2013-03-05 16:43   ` Ben Hutchings
2013-03-05 16:43     ` Ben Hutchings
2013-03-05 17:15     ` Eliezer Tamir
2013-03-05 19:57       ` David Miller
2013-03-05 19:55     ` David Miller
2013-03-05 20:03       ` H. Peter Anvin
2013-03-05 20:03         ` H. Peter Anvin
2013-02-27 17:56 ` [RFC PATCH 2/5] tcp: add TCP support for low latency receive poll Eliezer Tamir
2013-03-05 17:13   ` Ben Hutchings
2013-03-05 17:13     ` Ben Hutchings
2013-02-27 17:56 ` [RFC PATCH 3/5] ixgbe: Add support for ndo_ll_poll Eliezer Tamir
2013-02-27 18:41   ` Eric Dumazet
2013-02-27 19:20     ` Eliezer Tamir
2013-03-05 17:26   ` Ben Hutchings
2013-03-05 17:26     ` Ben Hutchings
2013-03-05 17:28     ` Ben Hutchings
2013-03-05 17:28       ` Ben Hutchings
2013-03-05 17:36       ` Eric Dumazet
2013-03-05 17:36         ` Eric Dumazet
2013-02-27 17:56 ` [RFC PATCH 4/5] ixgbe: add extra stats " Eliezer Tamir
2013-02-27 17:56 ` [RFC PATCH 5/5] ixgbe: kprobes latency test module Eliezer Tamir
2013-02-27 18:07 ` [RFC PATCH 0/5] net: low latency Ethernet device polling Eliezer Tamir
2013-02-27 18:07   ` Eliezer Tamir
2013-02-27 18:13 ` Stephen Hemminger
2013-02-27 18:47   ` Tom Herbert
2013-02-27 19:17     ` Eliezer Tamir
2013-03-04 22:34       ` Ben Hutchings
2013-02-27 19:58 ` Rick Jones
2013-02-27 20:40   ` Eliezer Tamir
2013-02-27 21:42     ` Ben Greear
2013-02-28  8:38       ` Eliezer Tamir
2013-03-01 21:24 ` David Miller
2013-03-01 22:57   ` Tom Herbert
2013-03-02 17:02   ` Eliezer Tamir
2013-03-04  7:37 ` Cong Wang [this message]
2013-03-04  7:37   ` Cong Wang
2013-03-04  8:19   ` Eliezer Tamir
2013-03-04  8:46     ` Eliezer Tamir
2013-03-04 17:19 ` Stephen Hemminger

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=51344F54.8060809@gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=eliezer.tamir@linux.jf.intel.com \
    --cc=eliezer@tamir.org.il \
    --cc=hpa@zytor.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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 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.