From: mindentropy@gmail.com (mindentropy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Clarification regarding design of a device.
Date: Mon, 2 May 2011 23:32:15 +0530 [thread overview]
Message-ID: <201105022332.15319.mindentropy@gmail.com> (raw)
In-Reply-To: <BANLkTikNFkW7VvOyxM-j39Yud+ECeK8juQ@mail.gmail.com>
On Monday 02 May 2011 10:58:45 PM Mulyadi Santosa wrote:
>
> I am not keen regarding char/block device management, but I think you
> should separate those streams.
>
> How? Well, same thing like you open a same file twice, right? You're
> given two different file descriptor. After all, the "open", "read" and
> "write" handler of device IMHO always assume that we wanna achieve
> such different stream, right?
Although given two file descriptors when I write some content it will be on the
same file right? Shouldn't the same file analogy apply?
I thought about using file descriptors to separate streams, but have to take
care of ensuring completion of processing the buffer when closed. This I feel
should be done if the descriptor gets reused.
next prev parent reply other threads:[~2011-05-02 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:23 Clarification regarding design of a device mindentropy
2011-05-02 17:28 ` Mulyadi Santosa
2011-05-02 18:02 ` mindentropy [this message]
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=201105022332.15319.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 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.