Subject: RE: Data Channels
From: Michael McNamara (mac@verisity.com)
Date: Mon Jul 29 2002 - 17:36:35 PDT
Kevin Cameron x3251 writes:
> > From owner-sv-ec@server.eda.org Mon Jul 29 14:16:51 2002
> >
> > Kevin-
> >
> > Some comments below... (My comments in blue).
> >
> > BTW - I propose that everyone use plain text for email
> > discussions -- makes it much more straightforward to read & post
> > replies. Strange formatting below is due to original HTML
> > formatting of email.
> >
> > Stuart
>
> >> So a SystemC channel is more like a subclass of module than the
> >> pipe-like channel I was thinking of.
> >
> > Yes, but the intent (similar to SystemVerilog "interfaces") is
> > that users then model the specific communications mechanisms they
> > desire using the basic channel construct.
>
> But it still doesn't look much like what you get from Unix pipe &
> socket calls.
My comments are in black ascii on a white background (at least as I
type them; (YCMV) your colors may vary :-)
I've kind of been waiting for this to be stated by some one.
What the SV-CC guys are working on is essentially exposing the C
library natively to Verilog. There are definiatly details to be
hashed out (how do you deal with a pointer returned from a C library
call, other than treat it as a handle?).
However within the framework being described, and using pass by
reference, it seems to me that you can call a lot of accept(2),
bind(2), connect(2), getprotoent(3), getsockname(2), getsockopt(2),
ioctl(2), listen(2), read(2), recv(2), select(2), send(2),
shutdown(2), socketpair(2), write(2) directly from SystemVerilog.
This archive was generated by hypermail 2b28 : Mon Jul 29 2002 - 17:38:21 PDT