mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dinesh Ahuja <mdlinux7@yahoo.co.in>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Share Wait Queue between different modules ?
Date: Wed, 18 May 2005 11:45:03 -0400	[thread overview]
Message-ID: <1116431103.5014.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20050518150200.88195.qmail@web8506.mail.in.yahoo.com>

On Wed, 2005-05-18 at 16:02 +0100, Dinesh Ahuja wrote:
> Thanks Steven for answer.
> 
> Could please tell me know how to share wait queue
> between different modules and where will be pratical
> implementation of that case.

A wait_queue is where a task goes while waiting for some event. If you
want to share it among modules you first need to determine where the
wait queue would be declared.  If module A and module B use the same
wait queue, and module A has declared it. Then module B would be
dependent on module A.  Module A would also have to export the wait
queue via the EXPORT_SYMBOL macro.  Or, the wait queue can be declared
in the kernel itself and all modules can use it. 

As for a practical implementation for doing this, I'm not sure what you
are asking for since the question itself is quite abstract.  I haven't
needed to export a wait queue from one module to the next. The best I
can tell you is if one module supplies some functionality or driver for
some device that has a wait queue for some event, and another module
adds functionality or a sub system of the device that needs to have
tasks wait on the same event, then I guess that would be one case.

-- Steve



  reply	other threads:[~2005-05-18 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 15:02 Dinesh Ahuja
2005-05-18 15:45 ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 15:11 Dinesh Ahuja
2005-05-16 17:01 ` Steven Rostedt

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=1116431103.5014.7.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdlinux7@yahoo.co.in \
    /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

Powered by JetHome