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