From: David Miller <davem@davemloft.net>
To: eliezer.tamir@linux.intel.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, donald.c.skidmore@intel.com,
e1000-devel@lists.sourceforge.net, willemb@google.com,
erdnetdev@gmail.com, bhutchings@solarflare.com,
andi@firstfloor.org, hpa@zytor.com, eilong@broadcom.com,
or.gerlitz@gmail.com, amirv@mellanox.com, alexr@mellanox.com,
eliezer@tamir.org.il
Subject: Re: [PATCH v4 net-next] net: poll/select low latency socket support
Date: Tue, 25 Jun 2013 16:36:14 -0700 (PDT) [thread overview]
Message-ID: <20130625.163614.1867701213174099145.davem@davemloft.net> (raw)
In-Reply-To: <20130624072803.26134.41593.stgit@ladj378.jer.intel.com>
From: Eliezer Tamir <eliezer.tamir@linux.intel.com>
Date: Mon, 24 Jun 2013 10:28:03 +0300
> select/poll busy-poll support.
>
> Split sysctl value into two separate ones, one for read and one for poll.
> updated Documentation/sysctl/net.txt
>
> Add a new poll flag POLL_LL. When this flag is set, sock_poll will call
> sk_poll_ll if possible. sock_poll sets this flag in its return value
> to indicate to select/poll when a socket that can busy poll is found.
>
> When poll/select have nothing to report, call the low-level
> sock_poll again until we are out of time or we find something.
>
> Once the system call finds something, it stops setting POLL_LL, so it can
> return the result to the user ASAP.
>
> Signed-off-by: Eliezer Tamir <eliezer.tamir@linux.intel.com>
Looks good, applied, thanks!
next prev parent reply other threads:[~2013-06-25 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:27 [PATCH v4 net-next 0/1] net: lls select poll support Eliezer Tamir
2013-06-24 7:28 ` [PATCH v4 net-next] net: poll/select low latency socket support Eliezer Tamir
2013-06-25 23:36 ` David Miller [this message]
2013-06-28 0:25 ` Cody P Schafer
2013-06-28 0:29 ` Cody P Schafer
2013-06-28 6:00 ` Eliezer Tamir
2013-06-28 4:43 ` Andi Kleen
2013-06-28 5:32 ` Eliezer Tamir
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=20130625.163614.1867701213174099145.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexr@mellanox.com \
--cc=amirv@mellanox.com \
--cc=andi@firstfloor.org \
--cc=bhutchings@solarflare.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eilong@broadcom.com \
--cc=eliezer.tamir@linux.intel.com \
--cc=eliezer@tamir.org.il \
--cc=erdnetdev@gmail.com \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--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 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).