All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org
Subject: [PATCH 0/6] Convert some GFP_ATOMIC allocations
Date: Fri, 13 Apr 2012 16:49:36 +0300	[thread overview]
Message-ID: <1334324982-3143-1-git-send-email-ja@ssi.bg> (raw)

	Convert mostly schedulers and one place for timeout table.
Only one place is left: register_ip_vs_proto_netns. I hope
someone will fix it together with other changes.

Julian Anastasov (6):
  ipvs: timeout tables do not need GFP_ATOMIC allocation
  ipvs: SH scheduler does not need GFP_ATOMIC allocation
  ipvs: DH scheduler does not need GFP_ATOMIC allocation
  ipvs: LBLC scheduler does not need GFP_ATOMIC allocation on init
  ipvs: LBLCR scheduler does not need GFP_ATOMIC allocation on init
  ipvs: WRR scheduler does not need GFP_ATOMIC allocation

 net/netfilter/ipvs/ip_vs_dh.c    |    2 +-
 net/netfilter/ipvs/ip_vs_lblc.c  |    2 +-
 net/netfilter/ipvs/ip_vs_lblcr.c |    2 +-
 net/netfilter/ipvs/ip_vs_proto.c |    2 +-
 net/netfilter/ipvs/ip_vs_sh.c    |    2 +-
 net/netfilter/ipvs/ip_vs_wrr.c   |    2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2012-04-13 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 13:49 Julian Anastasov [this message]
2012-04-13 13:49 ` [PATCH 1/6] ipvs: timeout tables do not need GFP_ATOMIC allocation Julian Anastasov
2012-04-13 13:49 ` [PATCH 2/6] ipvs: SH scheduler does " Julian Anastasov
2012-04-13 13:49 ` [PATCH 3/6] ipvs: DH " Julian Anastasov
2012-04-13 13:49 ` [PATCH 4/6] ipvs: LBLC scheduler does not need GFP_ATOMIC allocation on init Julian Anastasov
2012-04-13 13:49 ` [PATCH 5/6] ipvs: LBLCR " Julian Anastasov
2012-04-13 13:49 ` [PATCH 6/6] ipvs: WRR scheduler does not need GFP_ATOMIC allocation Julian Anastasov

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=1334324982-3143-1-git-send-email-ja@ssi.bg \
    --to=ja@ssi.bg \
    --cc=horms@verge.net.au \
    --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.