netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: netdev@vger.kernel.org
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] socket.7: add description for SO_BUSY_POLL
Date: Wed, 10 Jul 2013 12:55:19 +0000	[thread overview]
Message-ID: <u0lr4f6h8w8.fsf@orc05.imf.au.dk> (raw)
In-Reply-To: 20130710121745.13118.86907.stgit@ladj378.jer.intel.com

Eliezer Tamir <eliezer.tamir@linux.intel.com> writes:

> +While busy polling my improve latency of some application, care must be
> +taken when using it since this will increase both CPU utilization power usage.

s/my/may/; missing 'and' before 'power usage'. [And should
'application' be plural?]

Rasmus

      reply	other threads:[~2013-07-10 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 12:17 [PATCH] socket.7: add description for SO_BUSY_POLL Eliezer Tamir
2013-07-10 12:55 ` Rasmus Villemoes [this message]

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=u0lr4f6h8w8.fsf@orc05.imf.au.dk \
    --to=linux@rasmusvillemoes.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).