From: "Alok Singh" <aloks@broadcom.com>
To: "Andrew Lunn" <andrew@lunn.ch>, "Gary Thomas" <gary@mlbassoc.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Net BSD network stack posix tasks -
Date: Wed, 30 May 2007 17:53:00 -0000 [thread overview]
Message-ID: <FE7FB54DCB7C6949A1D3F9FF22DA6C135AB121@lvl7in-mail01.lvl7.com> (raw)
In-Reply-To: <20070530155621.GA32489@lunn.ch>
I guess I need to register to the list with some non-official mail id.
:-)
Ok. But My original question remains unanswered. Am I allowed to
convert the network cyg threads to posix threads, in case I want to do
it??
regards,
Alok
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Wednesday, May 30, 2007 9:26 PM
To: Gary Thomas
Cc: Alok Singh; ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Net BSD network stack posix tasks -
On Wed, May 30, 2007 at 09:42:20AM -0600, Gary Thomas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alok Singh wrote:
> > Gary,
> > To give an example, I'm required to make a posix call in the
> > end_send function below. end_send will be called by the network
stack to
> > send the out to Ethernet driver( layers below network layer to be
> > precise). What will be happen in this case? Wouldn't the system
crash
> > because of it??
>
> Why would you be calling some POSIX function from this code? That's
> most certainly not right (and is a layering violation). What are you
> trying to accomplish that the standard stack and I/O functions (e.g.
> select) cannot provide?
Im guessing here, but i think there "Ethernet" driver is actually not
an Ethernet driver. It is something a lot more complex and it just
emulates being Ethernet. This is broadcom after all. I guess they have
existing code which used to run in user space on Unix/POSIX and used
TAP/TUN to pass packets to the kernel. They are now trying to push
that code down into "kernel" space of the BSD stack and finding out
why it was a bad idea.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-30 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 17:11 Alok Singh
2007-05-29 17:20 ` Gary Thomas
2007-05-29 17:26 ` Robin Randhawa
2007-05-30 0:00 ` Nick Garnett
2007-05-30 11:59 ` Alok Singh
2007-05-30 13:07 ` Gary Thomas
2007-05-30 15:42 ` Alok Singh
2007-05-30 15:56 ` Gary Thomas
2007-05-30 16:33 ` Andrew Lunn
2007-05-30 17:53 ` Alok Singh [this message]
2007-05-30 18:14 ` Andrew Lunn
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=FE7FB54DCB7C6949A1D3F9FF22DA6C135AB121@lvl7in-mail01.lvl7.com \
--to=aloks@broadcom.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).