Re: [RTnet-developers] Test programs for SOCK_RAW and ETH_P_ALL

[Jorge A. <j-a...@cr...>]

Jan,

In attach follows the test cases for the SOCK_RAW and ETH_P_ALL features. Its two files written in C code.
One for sending messages, and other to read they using the ETH_P_ALL feature.

Please test the patch i send to you, after the refactoring that you need to do, and comment.

The problem about the sending messages still happen, i only can send 16 messages. Please check if you have the same problem in one of your machines.

In the loopback device i can send several messages (my test send 1000) but none is received in the rcv program. 
The loopback device works in a different way?

Em Segunda, 11 de Setembro de 2006 18:36, o Jan Kiszka escreveu:
> Jorge Almeida wrote:
> > OK.
> > 
> > I checkout the SVN and made the diff (it's in attach).
> 
> Sigh, your patch reverts a bulk of changes I made over the last weeks.
> This will need some cleanup first.
> 
> What about the test cases? Would be very helpful now to check if things
> work as expected after the refactoring.
> 
> > 
> > The RAW_SOCKET and ETH_P_ALL features are already mixed in the code. I must return to an early stage to generate two different patches.
> > But i send you a pach only for RAW_SOCKET some time ago (28-08-2006). That code didn't change.
> 
> Despite my remarks? Mmh...
> 
> > 
> > 
> > Regarding the other question in the last e-mail, about the queue behaviour, i can only send 16 messages, after that the send function return -105 for error code for every message that i try to send.
> > Error 105 - No Buffer Space Available. 
> > Even using 0x1234 has protocol type to send the messages.
> > But using this type of protocol the messages are only sended to the reading buffer, and not to the writting too.
> 
> Let me check if I understood this correctly: Although there cannot
> arrive any packets to the send-only socket now, it still runs out of
> buffers? Can you reproduce such problem over the loopback device as
> well? I'm asking as the best thing to analyse this issue now is to have
> a free-standing test case.
> 
> Jan
> 
> 

-- 
Jorge Almeida
j-a...@cr...

DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software, SA.