From: Mike Fedyk <mfedyk@matchmail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
Manfred Spraul <manfred@colorfullife.com>,
lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH] use rcu for fasync_lock
Date: Fri, 2 Jan 2004 17:09:09 -0800 [thread overview]
Message-ID: <20040103010909.GI1882@matchmail.com> (raw)
In-Reply-To: <20040102224150.GA5864@mail.shareable.org>
On Fri, Jan 02, 2004 at 10:41:50PM +0000, Jamie Lokier wrote:
> The best way is to maintain poll state in each "struct file". The
> order of complexity for the bitmap scan is still significant, but
> ->poll calls are limited to the number of transitions which actually
> happen.
What's the drawback to this approach?
Where is the poll state kept now?
> I think somebody, maybe Richard Gooch, has a patch to do this that's
> several years old by now.
Why wasn't it merged?
Implementation issues?
next prev parent reply other threads:[~2004-01-03 1:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 18:20 [RFC,PATCH] use rcu for fasync_lock Manfred Spraul
2003-12-20 21:10 ` [Lse-tech] " Stephen Hemminger
2003-12-20 21:35 ` Manfred Spraul
2003-12-21 11:36 ` Jamie Lokier
2003-12-21 12:40 ` Manfred Spraul
2003-12-21 14:14 ` Jamie Lokier
2003-12-21 14:59 ` Manfred Spraul
2003-12-21 15:08 ` Jamie Lokier
2004-01-02 21:15 ` Bill Davidsen
2004-01-02 22:41 ` Jamie Lokier
2004-01-03 1:09 ` Mike Fedyk [this message]
2004-01-03 21:28 ` Jamie Lokier
2004-01-04 19:01 ` Ingo Oeser
2004-01-04 19:20 ` Davide Libenzi
2004-01-05 21:17 ` Ingo Oeser
2004-01-05 22:24 ` Davide Libenzi
2003-12-21 15:14 ` Davide Libenzi
2003-12-21 15:17 ` Davide Libenzi
2003-12-21 15:28 ` Jamie Lokier
2003-12-21 18:38 ` OGAWA Hirofumi
2003-12-21 19:14 ` Manfred Spraul
2003-12-21 20:51 ` Linus Torvalds
2003-12-21 21:08 ` Manfred Spraul
2003-12-21 21:19 ` Linus Torvalds
2003-12-21 21:54 ` Manfred Spraul
2003-12-21 22:05 ` Linus Torvalds
2003-12-25 1:21 ` Manfred Spraul
2003-12-25 15:11 ` OGAWA Hirofumi
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=20040103010909.GI1882@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidsen@tmr.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manfred@colorfullife.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