From: Eric Dorman eld@jewel.ucsd.edu
Subject: [9fans] Re: etherelnk3.c
Date: Mon, 15 Dec 1997 09:43:11 -0800 [thread overview]
Message-ID: <19971215174311.p0Hq7y3GxIDWo02tu7GzSB-T-ITUtM4smUCkxLs53CM@z> (raw)
> From: "G. David Butler" <gdb@dbSystems.com>
> To: 9fans@cse.psu.edu
> Subject: [9fans] Re: etherelnk3.c
>
> Hello All!
>
> I've just started the process of back porting the brazil
> etherelnk3 driver to Plan9. I would like some feedback
> from this list (9fans) about some of the porting issues.
[xxx]
> After a quick perusal of the code, we have a big decision
> to make. This brazil driver does not use RingBuf, it uses
> Blocks. It also moves the Ctlr structure out of ether.h
> and into the driver .c file. The former change allows
> more data to be buffered and the latter allows driver
> specific data to be localized. These are both "good" things.
> Devether.c is not compatible with either of these changes,
> so we have to either update the entire ethernet subsystem to
> use Blocks, or make this driver use RingBufs and dirty the
> ether.h Card and Ctlr structures with the overhead of this
> driver.
Another thing to consider is how these changes would affect
the integration of ether drivers between the fs and terminal code.
Integrating these two trees first allieviates a whole mess of
existing problems and ensures that this type of effort won't
have to be done again (perhaps differently, even) for fs.
> David Butler
> gdb@dbSystems.com
Regards,
Eric L. Dorman
University of California at San Diego
edorman@ucsd.edu
next reply other threads:[~1997-12-15 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-15 17:43 Eric [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-01-02 21:54 jim
1997-12-31 17:14 Eric
1997-12-31 15:10 jim
1997-12-31 8:54 Nigel
1997-12-31 6:49 G.David
1997-12-31 5:16 jim
1997-12-31 3:51 G.David
1997-12-31 2:41 jim
1997-12-30 19:05 Eric
1997-12-30 1:20 G.David
1997-12-29 20:25 Eric
1997-12-24 4:30 jim
1997-12-15 18:14 G.David
1997-12-14 16:37 G.David
1997-12-13 18:04 G.David
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=19971215174311.p0Hq7y3GxIDWo02tu7GzSB-T-ITUtM4smUCkxLs53CM@z \
--to=9fans@9fans.net \
/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).