From: soyoung@taonetworks.com
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org
Subject: [Q]About using Netlink socket and endian transition..
Date: Thu, 24 Apr 2003 21:24:09 +0900 [thread overview]
Message-ID: <20030424122408.GB60541@taonetworks.com> (raw)
(This mail is CC'ed to linux-net mailing list)
Hi, I have a question about netlink socket.
It can be a 'stupid' question, but I need help about it.
The question is :
"Does it matter to change endian in netlink socket communication?"
Usually there is no endian-transition code in netlink socket program,
but netlink socket is also 'socket', so I think when I want to use
netlink communication, I have to use endian transition, but no one did it! :)
I'm testing netlink socket for Traffic Control (TC) in MPC8250,
which is a Motorola PowerPC based CPU.
TC works good in normal Pentium-based PC,
but it doesn't look working very well on MPC8250 - Traffics cannot recognize
their own filters when running through the linux router.
So I wonder whether this problem is related to netlink endian transition.
Is there anybody who has tested netlink socket in PPC-based platform?
Thanks.
reply other threads:[~2003-04-24 12:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030424122408.GB60541@taonetworks.com \
--to=soyoung@taonetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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).