On Wed, 2008-07-16 at 23:12 +0100, Al Viro wrote:I am curious though, in the general case of taking stuff off the wire and doing work on it in-place. Would you suggest two structs for things like this, one in cpu-order and one with the endian annotations, then the one place where you receive can do appropriate endian conversion using a pointer to a wire-endian struct and the rest of the code just uses the cpu-endian struct everywhere? Just a general design question. In the DLM case, these util functions are only used in 1-2 places each so it wouldn't be too bad to fold them into the receive/send paths, but you still need to byteswap somewhere, just curious what you are suggesting. Harvey --
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
