From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Michael Buesch <freesoftwaredeveloper@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serial port over TCP/IP
Date: Sun, 6 Apr 2003 14:46:47 +0100 [thread overview]
Message-ID: <20030406134647.GK639@gallifrey> (raw)
In-Reply-To: <200304061539.00494.freesoftwaredeveloper@web.de>
* Michael Buesch (freesoftwaredeveloper@web.de) wrote:
> On Sunday 06 April 2003 15:11, Dr. David Alan Gilbert wrote:
> > I keep thinking that it would be nice to have a mechanism for user space
> > char devices; it would have to have a mechanism to pass all the ioctls
> > to the process that dealt with it.
>
> But wouldn't this make too much overhead, if implemented all in userspace?
> I say this, because nbd is also implemented in user- und kernel-space.
Sure it would have overhead; but it would be a general mechanism and
mean that the kernel didn't need lots of char drivers (except for boot
time things). Lots of devices are really just filters/wrappers over
other more basic devices (look at the growing pile of USB serial
device drivers). Most char devices have such a low throughput that the
little overhead wouldn't make much difference, but would simplify the
kernel.
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2003-04-06 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 12:47 Michael Buesch
2003-04-06 13:11 ` Dr. David Alan Gilbert
2003-04-06 13:39 ` Michael Buesch
2003-04-06 13:46 ` Dr. David Alan Gilbert [this message]
2003-04-06 13:35 ` Rob van Nieuwkerk
2003-04-06 13:41 ` Michael Buesch
[not found] ` <200304062247.45525.freesoftwaredeveloper@web.de>
[not found] ` <20030406161206.A12616@uph.com>
2003-04-06 21:30 ` Michael Buesch
2003-04-07 2:37 ` H. Peter Anvin
2003-04-07 14:53 ` Michael Buesch
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=20030406134647.GK639@gallifrey \
--to=gilbertd@treblig.org \
--cc=freesoftwaredeveloper@web.de \
--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®