From: mindentropy@gmail.com (mindentropy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Clarification regarding design of a device.
Date: Mon, 2 May 2011 22:53:27 +0530 [thread overview]
Message-ID: <201105022253.27438.mindentropy@gmail.com> (raw)
Hi,
I have say a crypto device and if I pass a data stream assuming echo "test"
> /dev/aes and when I read it I get an encrypted output. Now if a program
opens the same device twice should and pass different streams should I
differentiate those 2 streams and have encrypted buffers of these 2 streams as
output? If yes how should I differentiate it? Or should I not differentiate and
provide different devices say aes0,aes1 or should the userspace program worry
about locking and sharing of resource?
Thanks.
next reply other threads:[~2011-05-02 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:23 mindentropy [this message]
2011-05-02 17:28 ` Clarification regarding design of a device Mulyadi Santosa
2011-05-02 18:02 ` mindentropy
2011-05-05 18:36 ` mindentropy
2011-05-05 23:22 ` Mulyadi Santosa
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=201105022253.27438.mindentropy@gmail.com \
--to=mindentropy@gmail.com \
--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).