From: "Luís Henriques" <lhenriques@criticalsoftware.com>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: copy to user
Date: Wed, 21 Nov 2001 11:02:39 +0000 [thread overview]
Message-ID: <200111211108.fALB8K291684@criticalsoftware.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0111202040180.23000-100000@mail.deis.isec.pt> <20011120144414.C1308@lynx.no>
In-Reply-To: <20011120144414.C1308@lynx.no>
> If you put the process in (un)interruptible sleep in the kernel, won't this
> be enough? This is different than SIGSTOP. Is the requirement that this
> process not leave the kernel call, or that it is actually consuming CPU
> cycles as well?
The process needs to be using CPU time, however, there must be a chance to
the scheduler to change the current process... if this occurs, than the delay
has to be aborted.
>
> > About using udelay... this soluction seemed fine to me at first but if I
> > hang the CPU with udelay the scheduler will no be doing it's job (isn't
> > it?). This would give me even more intrusiveness (another requirement:
> > the less intrusiveness as possible).
>
> It would probably work OK on an SMP system, since tasks can still be run
> on the other CPU.
>
> Cheers, Andreas
--
Luís Henriques
next prev parent reply other threads:[~2001-11-21 11:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 20:54 copy to user Luis Miguel Correia Henriques
2001-11-20 21:28 ` John Alvord
2001-11-20 21:44 ` Andreas Dilger
2001-11-21 11:02 ` Luís Henriques [this message]
2001-11-20 22:02 ` n0ano
2001-11-20 22:05 ` Chris Wright
2001-11-21 8:43 ` Mathijs Mohlmann
2001-11-21 10:12 ` Jan Hudec
-- strict thread matches above, loose matches on Subject: below --
2001-11-25 21:58 Marco C. Mason
2010-12-23 0:59 copy_to_user Hemanth Kumar
2010-12-23 1:18 ` copy_to_user Dexter Haslem
2010-12-23 2:15 ` copy_to_user Hemanth Kumar
2010-12-23 4:35 ` copy_to_user Srinivas G.
2010-12-23 5:18 ` copy_to_user Hemanth Kumar
2010-12-23 5:37 ` copy_to_user mukti jain
2010-12-23 12:21 ` copy_to_user Hemanth Kumar
2010-12-24 6:07 ` copy_to_user Hemanth Kumar
2010-12-24 7:59 ` copy_to_user Nilesh Tayade
2010-12-24 9:00 ` copy_to_user Dave Hylands
2010-12-24 9:20 ` copy_to_user Nilesh Tayade
2010-12-24 10:00 ` copy_to_user Hemanth Kumar
2010-12-24 9:26 ` copy_to_user Hemanth Kumar
[not found] <589679.60204.qm@web94707.mail.in2.yahoo.com>
2010-12-24 18:31 ` copy_to_user Mulyadi Santosa
2010-12-26 1:33 ` copy_to_user Hemanth Kumar
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=200111211108.fALB8K291684@criticalsoftware.com \
--to=lhenriques@criticalsoftware.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.