From: Martin Sustrik <sustrik@250bpm•com>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Alexander Viro <viro@zeniv•linux.org.uk>,
Sha Zhengju <handai.szj@taobao•com>,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org
Subject: Re: [PATCH 1/1] eventfd: implementation of EFD_MASK flag
Date: Fri, 08 Feb 2013 13:43:04 +0100 [thread overview]
Message-ID: <5114F2D8.5020300@250bpm.com> (raw)
In-Reply-To: <20130207144433.527ef024.akpm@linux-foundation.org>
On 07/02/13 23:44, Andrew Morton wrote:
> That's a nice changelog but it omitted a critical thing: why do you
> think the kernel needs this feature? What's the value and use case for
> being able to poll these descriptors?
To address the question, I've written down detailed description of the
challenges of the network protocol development in user space and how the
proposed feature addresses the problems.
It's too long to fit into ChangeLog, but it may be worth reading when
trying to judge the merit of the patch.
It can be found here: http://www.250bpm.com/blog:16
Martin
next parent reply other threads:[~2013-02-08 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1360219292-19754-1-git-send-email-sustrik@250bpm.com>
[not found] ` <20130207144433.527ef024.akpm@linux-foundation.org>
2013-02-08 12:43 ` Martin Sustrik [this message]
2013-02-08 22:21 ` [PATCH 1/1] eventfd: implementation of EFD_MASK flag Eric Wong
2013-02-09 2:40 ` Martin Sustrik
2013-02-09 3:54 ` Eric Wong
2013-02-09 7:36 ` Martin Sustrik
2013-02-09 11:51 ` Eric Wong
2013-02-09 12:04 ` Martin Sustrik
2013-02-07 23:29 Martin Sustrik
2013-02-15 2:45 ` Michał Mirosław
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=5114F2D8.5020300@250bpm.com \
--to=sustrik@250bpm$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=handai.szj@taobao$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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