From: markus93@inbox.ru (Meyer Lansky)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Prompt the account Scheduling O(1)
Date: Thu, 15 Jan 2015 18:57:20 +0300 [thread overview]
Message-ID: <1421337440.78541172@f152.i.mail.ru> (raw)
Hello!? E xcuse me for my english.
I study source code?scheduler O(1) code :
if (hardirq_count())
??????????????? per_cpu(cpu_hardirq_time, cpu) +=delta;
else if (in_serving_softirq() && !(curr->flags & PF_KSOFTIRQD))
??????????????? per_cpu(cpu_softirq_time, cpu) +=delta;
question: tell me what 's going on here ?
I have this code in paper form , so I can not give you a link to the code .
If there is a need to rewrite your page
please help !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150115/339846f7/attachment.html
next reply other threads:[~2015-01-15 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 15:57 Meyer Lansky [this message]
2015-01-15 17:39 ` Prompt the account Scheduling O(1) Valdis.Kletnieks at vt.edu
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=1421337440.78541172@f152.i.mail.ru \
--to=markus93@inbox.ru \
--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).