Passing data between threads.

[jenya7]

@jsulm said in Passing data between threads.:

@jenya7 said in Passing data between threads.:

I get - error: undefined reference to `vtable for READER'

Did you put your READER class into its own header file?
If so then please do a complete rebuild:

• Delete build folder
• Run qmake
• Build

Yes. I do - Add->Class and it generates reader.cpp and reader.h.
Thank you. Now it's OK.

[jenya7]

@Christian-Ehrlicher said in Passing data between threads.:

@jenya7 said in Passing data between threads.:

But this way the objects allocated on stack.

And what's the problem with it?

I don't know how the stack is configured and managed in a regular PC but in embedded systems it's a precious resource and there are many chances to run into a stack overflow.

[Christian Ehrlicher]

@jenya7 said in Passing data between threads.:

I don't know how the stack configured and managed in a regular PC but in embedded systems it's a precious resource and there are many chances to run into a stack overflow.

You should really get away from micro controller programming here. You've enough stack space, esp. on the outer most frame. Also print out the size of your UDP object - I would guess it's 8 bytes (mybe some more due to the vtable, but not that much)

[jenya7]

Well... I added a signal in UDP class

//in udp.h
signals:
    void ReadyForReader(const NET_PARAM& param, const QByteArray data);


//in udp.cpp
void UDP::ReadyRead()
{
    int size = static_cast<int>(socket->pendingDatagramSize());
    udp_buffer.resize(size);

    QHostAddress sender;
    quint16 senderPort;

    socket->readDatagram(udp_buffer.data(), udp_buffer.size(),
                         &sender, &senderPort);

    net_param.ip_str = sender.toString();
    net_param.port = senderPort;

    emit ReadyForReader(net_param, udp_buffer);
}

And a slot in READER class

class READER : public QObject
{
    Q_OBJECT

    public:
    READER(QObject *parent = nullptr);

    public slots:
    void ReadyForReader(const NET_PARAM& param, const QByteArray data);
};

//in reader.cpp
void READER::ReadyForReader(const NET_PARAM& param, const QByteArray data)
{
    qDebug() << "Message from IP: " << param.ip_str;
    qDebug() << "PORT: " << param.port;
    qDebug() << "Message number: " << counter;

   counter++;
}

I test it - send 8Kb datagram every 1 ms (total 6425 packets) - and I get it all. If I speed up - say every 500 us - a lot of datagrams are missed.
Actually I'm happy with the result.

[JonB]

@jenya7
And you expect that at a certain rate some UDP datagrams will be dropped, right?

[jenya7]

@JonB said in Passing data between threads.:

@jenya7
And you expect that at a certain rate some UDP datagrams will be dropped, right?

I would be happy to get all datagrams, no dropped at all.

[JonB]

@jenya7
Well, yes, but that wasn't what I was checking with you :) Of course we would all be happy to receive every datagram if we could! The point being is that UDP does not guarantee delivery/receipt, so I meant you are not surprised and are happy to live/understand this is the deal with drop-outs at faster speeds? One has no idea in questions here what users do/do not know/expect. We have had punters here who implement file transfer using UDP because it's "faster", and then they're not happy when they don't get all the file contents.....

[jenya7]

@JonB
Well. I get pretty impressive results. It would be impudence to complain about. :)

[Christian Ehrlicher]

If you remove the qDebug() output I would guess a lot fewer packets are being dropped. Add one (and not three) qDebug() every 1000 packets or so to get some numbers.

[jenya7]

@Christian-Ehrlicher said in Passing data between threads.:

If you remove the qDebug() output I would guess a lot fewer packets are being dropped. Add one (and not three) qDebug() every 1000 packets or so to get some numbers.

Packets should be stored in a file so qDebug() is some substitution for real actions.

[JonB]

@jenya7 said in Passing data between threads.:

Packets should be stored in a file so qDebug() is some substitution for real actions.

Point taken. However just FYI: I don't know how it's implemented, but qDebug() may be a bit "expensive", I assume it flushes output as it goes along. You are throwing quite a bit of data around frequently. If you are trying to process datagrams and can't keep up every bit of speed may help. If you can afford to write to file without flushing or syncing you may get better performance that you do now with qDebug()s. Obviously keep your necessary processing to a minimum.

[jenya7]

@JonB said in Passing data between threads.:

@jenya7 said in Passing data between threads.:

Packets should be stored in a file so qDebug() is some substitution for real actions.

Point taken. However just FYI: I don't know how it's implemented, but qDebug() may be a bit "expensive", I assume it flushes output as it goes along. You are throwing quite a bit of data around frequently. If you are trying to process datagrams and can't keep up every bit of speed may help. If you can afford to write to file without flushing or syncing you may get better performance that you do now with qDebug()s. Obviously keep your necessary processing to a minimum.

I thought about it. Printing to console is quite heavy.