From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Irfan Ullah (울라 이르판) <irfan@dke.khu.ac.kr>
Cc: greg@kroah.com, Ruben Safir <ruben@mrbrklyn.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: Software Prefetching using Machine learning
Date: Thu, 10 Oct 2019 01:43:13 -0400 [thread overview]
Message-ID: <206547.1570686193@turing-police> (raw)
In-Reply-To: <CA+mB8OwaC1ZQeX-KHTPeSG00AKE9Jy3mwwDUx15W-uttn9d+PQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]
On Thu, 10 Oct 2019 11:48:11 +0900, Irfan Ullah said:
> it can it be possible to share any type of data structure (e.g., structure,
> array, etc.) between kernel space C program and user space Python program
> in two way communication.
Python's split() is probably the wrong tool here. You probably are looking for
something like this:
https://pymotw.com/2/struct/ - the guys at Python Module Of The Week have you covered.
And a more detailed write-up:
http://archive.oreilly.com/oreillyschool/courses/Python3/Python3-08.html
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-10 5:43 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 [this message]
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
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=206547.1570686193@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=irfan@dke.khu.ac.kr \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.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;
as well as URLs for NNTP newsgroup(s).