Hi Jason, On Thu, Dec 08, 2016 at 11:20:04PM +0100, Jason A. Donenfeld wrote: > Hi David, > > On Thu, Dec 8, 2016 at 1:37 AM, David Miller <davem@xxxxxxxxxxxxx> wrote: > > You really have to land the IP header on a proper 4 byte boundary. > > > > I would suggest pushing 3 dummy garbage bytes of padding at the front > > or the end of your header. > > Are you sure 3 bytes to get 4 byte alignment is really the best? It's always the best. However there's another option which should be considered : maybe it's difficult but not impossible to move some bits from the current protocol to remove one byte. That's not always easy, and sometimes you cannot do it just for one bit. However after you run through this exercise, if you notice there's really no way to shave this extra byte, you'll realize there's no room left for future extensions and you'll more easily accept to add 3 empty bytes for this, typically protocol version, tags, qos or flagss that you'll be happy to rely on for future versions of your protocol. Also while it can feel like you're making your protocol less efficient, keep in mind that these 3 bytes only matter for small packets, and Ethernet already pads small frames to 64 bytes, so in practice any IP packet smaller than 46 bytes will not bring any extra savings. Best regards, Willy
