Kernelnewbies Digest, Vol 64, Issue 4
Quoted 95 lines · On Thu, Mar 3, 2016 at 10:07 PM, <[email protected]>…
Send Kernelnewbies mailing list submissions to
kernelnewbies at kernelnewbies.orgTo subscribe or unsubscribe via the World Wide Web, visit
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request at kernelnewbies.orgYou can reach the person managing the list at
kernelnewbies-owner at kernelnewbies.orgWhen replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Submitting patches to non-staging (Christoph Lameter)
2. Re: Submitting patches to non-staging (Pratyush Patel)
3. Fw: new important message (bear.yogi at gmx.de)
4. Re: where is disk block access in kernel ? (Mulyadi Santosa)
5. Re: where is disk block access in kernel ? (Valdis.Kletnieks at vt.edu)
6. remote system call (Nitin Varyani)
7. Re: remote system call (Mulyadi Santosa)----------------------------------------------------------------------
Message: 1
Date: Wed, 2 Mar 2016 13:45:54 -0600 (CST)
From: Christoph Lameter <[email protected]>
Subject: Re: Submitting patches to non-staging
To: Pratyush Patel <[email protected]>
Cc: kernelnewbies at kernelnewbies.org
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCIIQuoted 9 lines · Pratyush Patel
I will be pursuing my undergraduate thesis research in the field of real-time (operating) systems and as such, I expect to be closely involved with the timer and interrupt subsystems in Linux (as well as other areas, but to a lesser degree). I am also hoping to work with the hrtimer subsystem, and while going through the latest code (4.5-rc6) of the same, I found a very minor code-level change that could be incorporated (redundant #ifdef). Would such a change in a core kernel file be acceptable coming from a beginner? Or should I aim for the staging drivers first?
Dont worry about staging. There is no staing for interrupts and timers. Go direct and post to the relevant maintainers and lkml
Quoted 1 line
I very much look forward to contributing my first patch!
love to see it.
------------------------------
Message: 2
Date: Thu, 3 Mar 2016 07:20:18 +0530
From: Pratyush Patel <[email protected]>
Subject: Re: Submitting patches to non-staging
To: Christoph Lameter <[email protected]>
Cc: kernelnewbies <[email protected]> Message-ID:
<CAAnMKKbXAKUDHXx7Mf-npnM1BRWVbNoA=
BcZFB-xu5r6Ay46dA at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8Quoted 12 lines · Christoph Lameter
Quoted 9 lines · Pratyush Patel
I will be pursuing my undergraduate thesis research in the field of real-time (operating) systems and as such, I expect to be closely involved with the timer and interrupt subsystems in Linux (as well as other areas, but to a lesser degree). I am also hoping to work with the hrtimer subsystem, and while going through the latest code (4.5-rc6) of the same, I found a very minor code-level change that could be incorporated (redundant #ifdef). Would such a change in a core kernel file be acceptable coming from a beginner? Or should I aim for the staging drivers first?
Quoted 1 line
Dont worry about staging. There is no staing for interrupts and timers.
Go
Quoted 6 lines
direct and post to the relevant maintainers and lkml
Quoted 1 line
I very much look forward to contributing my first patch!
love to see it.
Quoted 9 lines
Here's the archive link:
http://comments.gmane.org/gmane.linux.kernel/2165466Please do let me know in case I did something wrongly.
Awaiting for it to be accepted!
It seems to be a valid change and should be accepted in the kernel.
You may probably change the commit message something like..
" removing nested macro definition (CONFIG_SMP)" if you want. good luck
-- Vishwas
Quoted 250 lines
------------------------------
Message: 3
Date: Thu, 3 Mar 2016 05:37:11 +0300
From: <[email protected]>
Subject: Fw: new important message
To: "kernelnewbies" <[email protected]>, "leo kirotawa"
<[email protected]>, "lifelong0811" <[email protected]>, "lind.lampe at gmx.de" <[email protected]>, "linux-api" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"Hello!
New message, please read <http://majorinvesting.com/longer.php?drpr>
bear.yogi at gmx.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/043f8012/attachment-0001.html------------------------------
Message: 4
Date: Thu, 3 Mar 2016 13:18:42 +0700
From: Mulyadi Santosa <[email protected]>
Subject: Re: where is disk block access in kernel ?
Cc: kernelnewbies <[email protected]> Message-ID:<CAGdaadaDSooo8f7LBO-v09kO8qmfh4pZ58VsVY0E+2fqqQhJHw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"Quoted 12 lines · Ran Shalit
Hello,
I would like to monitor the write access to disk blocks (so that I can monitor the block index in some bitmap)
I think this must be done in kernel (userspace have no such information) I have tried to search in kernel but did not found where is the API to access disk blocks.
There islibata-core.c, but I can't find such routines there, and neither any documentation.Is there any idea ?
Quoted 8 lines
Regards,
Ran_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbiesHi
Sounds like something doable via ftrace.
try to check if it is feasible to be done using ftrace
--
regards,Mulyadi Santosa
Freelance Linux trainer and consultantblog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.comThis email has been sent from a virus-free computer protected by Avast. www.avast.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmailQuoted 1 line
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/490aed0f/attachment-0001.html------------------------------
Message: 5
Date: Thu, 03 Mar 2016 02:09:39 -0500
From: Valdis.Kletnieks at vt.edu
Subject: Re: where is disk block access in kernel ?
To: Ran Shalit <[email protected]>
Cc: kernelnewbies <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"Quoted 2 lines · Ran Shalit
I would like to monitor the write access to disk blocks (so that I can monitor the block index in some bitmap)
What exactly are you trying to do with that information? (Hint - figure out how big a bitmap you need for the blocks on a 2T or 4T drive - or for the 600T to petabyte filesystems I deal with for a living).
Do you need just write access, or read as well?
Do you need the info before or after the disk cache is involved? Do you need to deal with corner cases like a program writing to a file, and then unlinking the file before the blocks are written to disk?As is common for kernel issues, the answer depends a lot on exactly what the *real* question is....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url :
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/67a25edc/attachment-0001.bin------------------------------
Message: 6
Date: Thu, 3 Mar 2016 16:42:24 +0530
From: Nitin Varyani <[email protected]>
Subject: remote system call
To: Kernel Newbies <[email protected]> Message-ID:<CAKfJ7KJCacyJyNeokCxG5rNCMB-j3bvu83YYe_pUYVofgTombg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"Hi,
I want to migrate user context of a process to a remote machine (i.e.
registers, code, data, virtual memory and program counter) and when it makes a system call or file i/o, I want to send that request to its home node.That is, the user process executing at remote node will copy desired system call number to %eax of home node and will execute 'int
0x80'. This will generate interrupt0x80which should be sent to home node and an interrupt service routine at home node will be called. This routine will execute in ring 0 of home node.A portion of process context which is system dependent has to be kept at the home node.
That is, link to open files and link to kernel stack.
For eg: the following portion of the
task_structhas to be kept at home node
/* filesystem information */struct fs_struct *fs; /* open file information */ struct files_struct *files;Is it feasible? Can someone show some more light into it?
Nitin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/892eabc6/attachment-0001.html------------------------------
Message: 7
Date: Thu, 3 Mar 2016 23:37:11 +0700
From: Mulyadi Santosa <[email protected]>
Subject: Re: remote system call
To: Nitin Varyani <[email protected]>
Cc: Kernel Newbies <[email protected]> Message-ID:
<CAGdaadZF-f7h6eEFW=
RsVrexorpudYawydPE2ibZLGzWOVzcQg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"Quoted 4 lines · Nitin Varyani
Hi,
I want to migrate user context of a process to a remote machine
(i.e. registers, code, data, virtual memory and program counter) and when it makes a system call or file i/o, I want to send that request to itshome
Quoted 22 lines
node.
That is, the user process executing at remote node will copy desired system call number to %eax of home node and will execute 'int
0x80'. This will generate interrupt0x80which should be sent to home node and an interrupt service routine at home node will be called. This routine will execute in ring 0 of home node.A portion of process context which is system dependent has to be kept at the home node.
That is, link to open files and link to kernel stack.
For eg: the following portion of the
task_structhas to be kept at home node
/* filesystem information */struct fs_struct *fs; /* open file information */ struct files_struct *files;Quoted 10 lines
Is it feasible? Can someone show some more light into it?
Nitin
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbiesFeasible, yes.
Try to check the source code of MOSIX/OpenMosix or OpenSSI.
Kerrighed is another project which done similar thing too.
--
regards,Mulyadi Santosa
Freelance Linux trainer and consultantblog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160303/8061dd13/attachment.html------------------------------
Quoted 9 lines
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbiesEnd of Kernelnewbies Digest, Vol 64, Issue 4
********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160304/39659ec4/attachment-0001.html