From: Melkor Ainur <melkorainur@yahoo.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: signal_pending() and schedule()
Date: Tue, 26 Mar 2002 19:52:05 -0800 (PST) [thread overview]
Message-ID: <20020327035205.57964.qmail@web21208.mail.yahoo.com> (raw)
In-Reply-To: <20020327014932.GB803@insight.us.oracle.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1298 bytes --]
Hi Joel, everyone,
Thanks for the info about the SIGALRM. I had not
noticed this until I did an strace on netscape.
I had been simple minded in my implementation of
tcp_sendmsg. For a userspace application such as
netscape, I allocate a kernel buffer(s)and copy the
data from user space into this/these buffer(s)
(because I am unaware of a way around singlecopy
when the app uses a userspace buffer). I then schedule
dma. After that I put the calling application to
sleep. I don't have a good idea of how I would
handle this if the application got woken up out of the
sleep by a signal before the dma was done. I suppose
I could spin but that seems unclean. I will
look through other drivers and see if/how this is
handled but any leads would be greatly appreciated.
Thanks,
Melkor
--- Joel Becker <Joel.Becker@oracle.com> wrote:
> A signal has arrived. Netscape's userspace
> "threading" is based
> entirely on signals. Netscape sends itself SIGALRM
> almost continuously.
> You'll have to expect this from Netscape and work
> around or with it.
>
> Joel
>
__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®
http://movies.yahoo.com/
prev parent reply other threads:[~2002-03-27 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 0:19 Melkor Ainur
2002-03-27 0:53 ` Alan Cox
2002-03-27 1:49 ` Joel Becker
2002-03-27 3:52 ` Melkor Ainur [this message]
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=20020327035205.57964.qmail@web21208.mail.yahoo.com \
--to=melkorainur@yahoo.com \
--cc=Joel.Becker@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®