From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Query on mechanisms to communicate between kernel modules in Linux
Date: Mon, 12 Feb 2018 11:25:05 +1100 [thread overview]
Message-ID: <20180212002505.GA16552@eros> (raw)
In-Reply-To: <CAODjBtr=bEkrN_DNY6jhXTxx0dg=nW-qzBb7WKkZhtSF=_Ezhg@mail.gmail.com>
On Sat, Feb 10, 2018 at 10:30:36PM +0530, Neil Thomas wrote:
> Thanks a lot. I will try out this.
Please don't top post. It upsets people.
Good luck,
Tobin.
> On 10-Feb-2018 2:08 PM, "Pintu Kumar" <pintu.ping@gmail.com> wrote:
>
> > On Fri, Feb 9, 2018 at 12:52 AM, Neil Thomas <neilkt27@gmail.com> wrote:
> > > Thanks, I will check it out.
> > >
> > > On 09-Feb-2018 12:50 AM, <valdis.kletnieks@vt.edu> wrote:
> > >>
> > >> On Thu, 08 Feb 2018 23:38:01 +0530, Neil Thomas said:
> > >>
> > >> > I am just a beginner. I have tried procfs, Netlink socket to
> > communicate
> > >> > between user space and kernel space and it works fine.
> > >> >
> > >> > I am developing a monitoring utility to trace the VFS operation and
> > find
> > >> > the frequency of VFS function calls. This monitoring utility runs in
> > >> > kernel
> > >> > space. We have to record the occurrence of each VFS function calls
> > >> > (like
> > >> > vfs_open(), vfs_read()). I don't know which is best mechanism to
> > >> > report
> > >> > this VFS event to the monitoring utility.
> > >> >
> > >> > Could anyone please suggest the best mechanism to transfer data
> > >> > frequently
> > >> > between kernel modules.
> >
> > You can also use ION (CONFIG_ION) or DMABUF (DMA_SHARED_BUFFER) buffer
> > sharing mechanism to share data between 2 drivers.
> > Check this:
> > https://www.kernel.org/doc/html/latest/driver-api/dma-buf.html
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> > linux.git/tree/drivers/staging/android/ion?h=v4.15
> >
> > >>
> > >> There's a perfectly good perf-based function trace facility that will
> > >> provide
> > >> this info to userspace.
> > >>
> > >> http://www.brendangregg.com/perf.html#StaticKernelTracing
> > >>
> > >
> > > _______________________________________________
> > > Kernelnewbies mailing list
> > > Kernelnewbies at kernelnewbies.org
> > > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> > >
> >
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2018-02-12 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 4:09 Query on mechanisms to communicate between kernel modules in Linux Neil Thomas
2018-02-08 14:26 ` Greg KH
2018-02-08 18:08 ` Neil Thomas
2018-02-08 19:20 ` valdis.kletnieks at vt.edu
2018-02-08 19:22 ` Neil Thomas
2018-02-10 8:38 ` Pintu Kumar
2018-02-10 17:00 ` Neil Thomas
2018-02-12 0:25 ` Tobin C. Harding [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=20180212002505.GA16552@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.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).