"Matthew Dillon" <[EMAIL PROTECTED]> wrote:
> :Unfortunately, I've found that having a group of processes reading from
a
> :group of socketpairs has better performance than having them all read
from
> :a single socketpair. I've been unable to determine why.
>
> The problem is that when you ha
Hello.
If we have a character device driver with and more than one
open handles for it, can read() and ioctl() choose which one
is used?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I have to agree here, one of the major issues in writing device drivers,
which I used to do for a living, is getting proper documentation for
the devices themselves. For something like video cards, it's even worse
because the cards change so rapidly. I can imagine that there will be some
issues
>
> Ah, indeed! nul/NUL == ascii. 'nil' should removed from our vocabulary.
>
NIL or nil, is the nil pointer from lisp. lisp is often the
first time many people start to understans that data can drive
programs. this is a good thing.
jmb
To Unsubscribe: send mail to [EMAIL PRO
:> Ah, indeed! nul/NUL == ascii. 'nil' should removed from our vocabulary.
:>
:
: NIL or nil, is the nil pointer from lisp. lisp is often the
:first time many people start to understans that data can drive
:programs. this is a good thing.
:
:jmb
I don't know anybody under the
"Scott Hess" <[EMAIL PROTECTED]> wrote:
> "Matthew Dillon" <[EMAIL PROTECTED]> wrote:
> > :Unfortunately, I've found that having a group of processes reading
> > :from a group of socketpairs has better performance than having
> > :them all read from a single socketpair. I've been unable to
> > :
-On [2124 00:00], Joachim Jäckel ([EMAIL PROTECTED]) wrote:
>
>Here´s some information to the card I'd like to support:
>
>It's a Miro DC10+ Video Grabber Card for Non-Linear Video-Editing.
>It uses a Siemens SAA7110, a Zoran 36060+36067 and a ADV chip to en-
>and decode the video-informat
:OK, so let's say I did spend some time implementing it in terms of semget()
:and semop(). Would you be totally apalled if the performance turned out to
:be about the same as using a single socketpair? Do you have a very strong
:feeling that it should be significantly better. [Again, under
:3.
"Brian D. Moffet" wrote:
> Okay, stupid question. socketpair returns 2 sockets which according to
> the man page are "indistinguishable". Does this mean that you can read and
> write to either socket pair?
Yep, you can write to either end and it will come out the other end.
> pipe(2) returns
* Matthew Dillon <[EMAIL PROTECTED]> [000125 11:51] wrote:
>
> :OK, so let's say I did spend some time implementing it in terms of semget()
> :and semop(). Would you be totally apalled if the performance turned out to
> :be about the same as using a single socketpair? Do you have a very strong
Okay, stupid question. socketpair returns 2 sockets which according to
the man page are "indistinguishable". Does this mean that you can read and
write to either socket pair?
pipe(2) returns 2 file descriptors, one of which is a read and one of
which is a write fd. The other end flips these a
Hi all,
I have a problem with 3.4-RELEASE on Compaq Deskpro machines
with new Fast Ethernet cards with i82559 chip.
I installed them from 3.4-R ISO image without problems noticed
(ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso).
I can use networking with Cisco router
"Alfred Perlstein" <[EMAIL PROTECTED]> wrote:
> I think you probably want to experiment with pools attached to the
> pipe, and you ought to be using pipe rather than socketpair.
My tests indicate that pipe performance in this case is identical to
socketpair performance. Perhaps because I'm sendi
On Tue, Jan 25, 2000 at 09:12:31AM -0800, Brian D. Moffet wrote:
> Okay, stupid question. socketpair returns 2 sockets which according to
> the man page are "indistinguishable". Does this mean that you can read and
> write to either socket pair?
Yes sir.
> pipe(2) returns 2 file descriptors,
On Wed, Jan 19, 2000 at 09:48:43AM -0600, Dan Nelson wrote:
> In the last episode (Jan 19), Charles Sprickman said:
>
> > More importantly, this machine is just sitting here waiting to be put
> > in production, so I'm more than willing to play around with it like
> > this while I still can...
>
Matt Dillon wrote:
>
> :> Ah, indeed! nul/NUL == ascii. 'nil' should removed from our vocabulary.
> :>
Jonathan Bresler wrote:
> :
> : NIL or nil, is the nil pointer from lisp. lisp is often the
> :first time many people start to understans that data can drive
> :programs. this
In article <[EMAIL PROTECTED]>
Luoqi Chen <[EMAIL PROTECTED]> writes:
> > I think it is difficult to implement such conversion because:
> >
> > - Not only bus space stuff also resource manager stuff need to
> > perform such conversion.
>
> Why? Both bus_space_handle_t and bus_space_tag_t
17 matches
Mail list logo
