Hi,
Correct me if I'm wrong, but in a high-level perspective I see that kni is
providing an option for applications to use their regular interfaces (e.g.
sockets) and abstracts the usage of pmds.
If this is somehow correct, are there any differences with regard to
performance benefits that can be
Additional question:
Apart from the possible fact that kni performs zero-copy in the driver
layer, does this also apply on the sockets layer, or does the sockets
operations (+ sys calls) are not avoided ? This is assuming that the
application uses regular sockets to read/write to knis.
Cheers,
P
Hi,
I would like to ask if kni was intentionally provided mainly for PMD API
users/developers ? Most of the examples emphasizes how to use the kni
devices by upper level applications with sockets, however I haven't seen
any usage where PMD APIs being used to send packets to knis. Is this
possibl
I want calculate the NIC rss hash result by function,but the result is not
right, I don't know where the wrong.
struct mbf_cb{
uint32_t sip;
uint32_t dip;
uint16_t sport;
uint16_t dport;
};
static uint8_t test_rss[]={
0x6d,0x5a,0x56,0xda,0x25,0x5b,0x0e,0
4 matches
Mail list logo