From: jtc@redback.com (J.T. Conklin)
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Make gdbserver use async I/O on Linux
Date: Thu, 21 Jun 2001 13:28:00 -0000 [thread overview]
Message-ID: <5mae317f26.fsf@jtc.redback.com> (raw)
In-Reply-To: <20010606140322.A29266@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <dmj+@andrew.cmu.edu> writes:
Daniel> The only problem I can think of that this might cause is if
Daniel> F_SETOWN is less portable than FASYNC. Apparently you need to
Daniel> do that explicitly on a Linux target before SIGIO will be
Daniel> sent.
The same is true on other targets as well.
I found that Greg McGary submitted a patch quite a long time ago to do
async i/o on Linux and additional targets that was never applied. I'm
going to rectify that problem and will commit it shortly.
--jtc
--
J.T. Conklin
RedBack Networks
prev parent reply other threads:[~2001-06-21 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 14:03 Daniel Jacobowitz
2001-06-06 23:34 ` Eli Zaretskii
2001-06-07 10:43 ` Daniel Jacobowitz
2001-06-07 11:38 ` Eli Zaretskii
2001-06-07 12:04 ` Daniel Jacobowitz
2001-06-08 0:37 ` Eli Zaretskii
2001-06-21 13:28 ` J.T. Conklin [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=5mae317f26.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.redhat.com \
/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