kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Irfan Ullah (울라 이르판)" <irfan@dke.khu.ac.kr>
Cc: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Kernel development tools (was Re: Software Prefetching using Machine learning)
Date: Thu, 10 Oct 2019 08:40:14 +0200	[thread overview]
Message-ID: <20191010064014.GA256567@kroah.com> (raw)
In-Reply-To: <CA+mB8OyM_cu1Owy9OukpVpZ1BU+heCiLSf0Rg60XTmUqMGRf2w@mail.gmail.com>

On Thu, Oct 10, 2019 at 03:21:46PM +0900, Irfan Ullah (울라 이르판) wrote:
> Thank you.
> You are absolutely right. As a freshman in the kernel development, and
> having experience in high level languages, things look complicated :(.
> Can you please suggest me what is the efficient and easy way to exchange
> data between kernel space and user space. I want the way in which the
> kernel should initiate the communication; the kernel daemon first sends the
> data to the user space daemon, and the user space daemon (waiting and
> listening to the kernel space daemon) receives and processes the data, and
> then sends feedback. There are many tools i.e., netlink
> (connectionless, asynchronous), ioctl, and /proc available.
> Which tool,  and library you suggest for performing the task? and How it
> could be done?
> I would be grateful if you could provide me with some links/examples/blogs.

I think you already have the list above (netlink, ioctl, proc), so just
start with those and see how it goes.

Note, the kernel can not "send userspace something and wait for it to
send a response" and expect to keep on working, as the kernel can never
wait for userspace to do something as that would cause it to stop.

Best of luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-10-10  6:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  3:37 Software Prefetching using Machine learning Irfan Ullah (울라 이르판)
2019-10-09  7:44 ` Greg KH
2019-10-09 19:08 ` Valdis Klētnieks
2019-10-10  0:21   ` Ruben Safir
2019-10-10  0:24   ` Ruben Safir
2019-10-10  2:10     ` Irfan Ullah (울라 이르판)
2019-10-10  2:48       ` Irfan Ullah (울라 이르판)
2019-10-10  5:43         ` Valdis Klētnieks
2019-10-10  5:51         ` Kernel development tools (was Re: Software Prefetching using Machine learning) Valdis Klētnieks
2019-10-10  6:21           ` Irfan Ullah (울라 이르판)
2019-10-10  6:40             ` Greg KH [this message]
2019-10-10 13:22       ` Software Prefetching using Machine learning Rik van Riel

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=20191010064014.GA256567@kroah.com \
    --to=greg@kroah.com \
    --cc=irfan@dke.khu.ac.kr \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    /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).