All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: Julian Anastasov <ja@ssi.bg>, lvs-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] Changes for PMTU Discovery
Date: Mon, 23 Jul 2012 12:45:45 +0200	[thread overview]
Message-ID: <20120723104545.GA4757@1984> (raw)
In-Reply-To: <20120723075949.GB9371@verge.net.au>

On Mon, Jul 23, 2012 at 04:59:49PM +0900, Simon Horman wrote:
> On Mon, Jul 23, 2012 at 10:33:24AM +0300, Julian Anastasov wrote:
> > 
> > 	Hello,
> > 
> > On Mon, 23 Jul 2012, Simon Horman wrote:
> > 
> > > On Fri, Jul 20, 2012 at 11:59:51AM +0300, Julian Anastasov wrote:
> > > > 	This patchset implements PMTU Discovery for TUN
> > > > packets and option to disable it.
> > > > 
> > > > Julian Anastasov (2):
> > > >   ipvs: implement passive PMTUD for IPIP packets
> > > >   ipvs: add pmtu_disc option to disable IP DF for TUN packets
> > > > 
> > > >  include/net/ip_vs.h             |   11 +++++
> > > >  net/netfilter/ipvs/ip_vs_core.c |   76 ++++++++++++++++++++++++++++++++++-
> > > >  net/netfilter/ipvs/ip_vs_ctl.c  |    8 ++++
> > > >  net/netfilter/ipvs/ip_vs_xmit.c |   83 ++++++++++++++++++++++++++------------
> > > >  4 files changed, 149 insertions(+), 29 deletions(-)
> > > 
> > > Thanks, I have applied these to ipvs-next.
> > > 
> > > There were some offsets when applying the patches
> > > and a conflict in the last hunk of ip_vs_xmit.c (in the first patch).
> > > Could you check to make sure everything went in ok?
> > 
> > 	I created it for net-next on the same day because
> > I saw this problem. Both patches apply even on net-next from
> > today. May be ipvs-next is outdated, net-next changes rapidly
> > last days. If you want to push these patches in this merge
> > window you have to update ipvs-next. If it is not possible
> > I'll resend after 2 weeks.
> 
> ipvs-next is based on Pablo's nf-next tree.
> So the timing of updating is up to him.

I just refreshed my tree. Let me know if this is what you needed.

Please, feel free to ping me whenever you need this.

  reply	other threads:[~2012-07-23 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  8:59 [PATCH 0/2] Changes for PMTU Discovery Julian Anastasov
2012-07-20  8:59 ` [PATCH 1/2] ipvs: implement passive PMTUD for IPIP packets Julian Anastasov
2012-07-20  8:59 ` [PATCH 2/2] ipvs: add pmtu_disc option to disable IP DF for TUN packets Julian Anastasov
2012-07-23  6:46 ` [PATCH 0/2] Changes for PMTU Discovery Simon Horman
2012-07-23  7:33   ` Julian Anastasov
2012-07-23  7:59     ` Simon Horman
2012-07-23 10:45       ` Pablo Neira Ayuso [this message]
2012-07-23 23:02         ` Simon Horman

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=20120723104545.GA4757@1984 \
    --to=pablo@netfilter.org \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.