From: Cort Dougan <cort@fsmlabs.com>
To: Pavel Roskin <pavel_roskin@geocities.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Disabling interrupts
Date: Thu, 23 Mar 2000 15:48:57 -0700 [thread overview]
Message-ID: <20000323154857.A11515@medea.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0003231654120.31863-100000@sunapee.transcept.com>; from Pavel Roskin on Thu, Mar 23, 2000 at 04:58:52PM -0500
For something like this rtl may be better suited for the task.
} Well, this code needs to read some data continously. Then the data must
} be processed and written to a file.
}
} If you expect problems, I could create a new syscall and pass a buffer to
} it. Probably this should be Ok. But the buffer can be huge (comparable
} with the RAM size), so I would like to avoid copying data. This means that
} the kernel needs to write to the userspace buffer directly.
}
} Thank you for the reply.
}
} Regards,
} Pavel Roskin
}
}
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-03-23 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-23 21:50 Disabling interrupts Pavel Roskin
2000-03-23 21:45 ` Cort Dougan
2000-03-23 21:58 ` Pavel Roskin
2000-03-23 22:31 ` Greg Johnson
2000-03-23 22:48 ` Cort Dougan [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=20000323154857.A11515@medea.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pavel_roskin@geocities.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;
as well as URLs for NNTP newsgroup(s).