Caching learned MSS/MTU values

[Hannes Frederic Sowa]

Hi Fred!

On Fri, Oct 25, 2013 at 11:05:14PM +0000, Templin, Fred L wrote:
> > -----Original Message-----
> > From: ipv6-ops-bounces+fred.l.templin=boeing.com at lists.cluenet.de [mailto:ipv6-ops-
> > bounces+fred.l.templin=boeing.com at lists.cluenet.de] On Behalf Of Hannes Frederic Sowa
> > Sent: Friday, October 25, 2013 1:49 PM
> > To: Templin, Fred L
> > Cc: Jason Fesler; IPv6 operators forum
> > Subject: Re: Caching learned MSS/MTU values
> > 
> > On Fri, Oct 18, 2013 at 10:23:00PM +0000, Templin, Fred L wrote:
> > > Hi Hannes,
> > >
> > > > Oh, that is interesting. I'll have a look at the weekend.
> > >
> > > OK. I had to roll another version to make some minor
> > > changes - see:
> > >
> > > http://linkupnetworks.com/seal/sealv2-0.2.tgz
> > > http://www.ietf.org/id/draft-templin-intarea-seal-64.txt
> > >
> > > I will let it rest for now, so this would be the version to
> > > start looking at. Let me know if there are any questions or
> > > comments.
> > 
> > Do you plan to convert them to git for easier patch management? I would
> > highly recommend it
> 
> Sure - do you have instructions on how to do this?

For git I would recommend reading some tutorial.
http://git-scm.com/documentation should help.

As these changes will have to go through net-next I would recommend cloning
the net-next repository: https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git

I would create a branch based on v3.10 and then git apply the patch (be aware
that git apply does not allow fuzz, so use git apply --reject if it does not
apply cleanly).

Check all the rejects and bring it in a compileable (better yet, stable
state). Then check if you can even break the giant patch up into smaller
independent parts. If it gets merged into the kernel you have to check
that each patch independently compiles and does not leave the logic in
some broken state (so that git bisect is still possible).

You could use gitk to stage seperate hunks and commit them independently.
Sending the patches for review as is as simple as a git send-email then.

Even if you don't plan to send it out for review soon this will make
rebasing the patch on more recent kernels more easily.

Greetings,

  Hannes