linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christof Meerwald <cmeerw@cmeerw.org>
To: "Paton J. Lewis" <palewis@adobe.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Jason Baron <jbaron@redhat.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paul Holland <pholland@adobe.com>,
	Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [PATCH] epoll: Improved support for multi-threaded clients
Date: Mon, 9 Jul 2012 20:45:39 +0200	[thread overview]
Message-ID: <20120709184539.GI7275@edge.cmeerw.net> (raw)
In-Reply-To: <6.2.5.6.2.20120629140909.04bb0a40@adobe.com>

On Fri, Jun 29, 2012 at 02:43:06PM -0700, Paton J. Lewis wrote:
> At 6/19/2012 11:17 AM, Christof Meerwald wrote:
> >But, taking one step back - wouldn't an alternative approach be to add
> >some mechanism to allow a thread to post a user-event for an fd? So in
> >delete_epoll_item you would post a user event (e.g. EPOLLUSER) for the
> >fd which you can then handle in your epoll_wait processing thread -
> >with no additional synchronisation necessary.
> I think this is an excellent suggestion, and in fact your proposal
> is more similar to what Windows provides when solving this problem.
> I'll test this idea out with our code and get back to you. Is there
> an existing kernel technique that you would recommend for posting a
> user event for an fd, or should I explore using epoll_ctl with
> EPOLL_CTL_MOD?

I don't know about any existing kernel technique for this, but my gut
feeling would be a new op value for epoll_ctl, maybe something like
EPOLL_CTL_TRIGGER.


Christof

-- 

http://cmeerw.org                              sip:cmeerw at cmeerw.org
mailto:cmeerw at cmeerw.org                   xmpp:cmeerw at cmeerw.org

  reply	other threads:[~2012-07-09 18:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 22:34 [PATCH] epoll: Improved support for multi-threaded clients Paton Lewis
2012-06-13 23:27 ` Andrew Morton
2012-06-18 21:58   ` Paton J. Lewis
2012-06-19 23:42     ` Andrew Morton
2012-06-16 18:47 ` Christof Meerwald
2012-06-18 23:24   ` Paton J. Lewis
2012-06-19 18:17     ` Christof Meerwald
2012-06-29 21:43       ` Paton J. Lewis
2012-07-09 18:45         ` Christof Meerwald [this message]
2012-08-03  1:37         ` Paton J. Lewis
2012-08-14 20:21           ` Christof Meerwald
2012-08-14 22:13             ` Paton J. Lewis

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=20120709184539.GI7275@edge.cmeerw.net \
    --to=cmeerw@cmeerw.org \
    --cc=davidel@xmailserver.org \
    --cc=jbaron@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palewis@adobe.com \
    --cc=pholland@adobe.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).