All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Vadai <amirv@mellanox.com>
To: David Miller <davem@davemloft.net>, <vgoyal@redhat.com>
Cc: <amirv@mellanox.com>, <andi@firstfloor.org>,
	<akpm@linux-foundation.org>, <netdev@vger.kernel.org>,
	<ogerlitz@mellanox.com>, <yevgenyp@mellanox.com>
Subject: Re: [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules
Date: Wed, 6 Aug 2014 11:10:18 +0300	[thread overview]
Message-ID: <53E1E2EA.6020102@mellanox.com> (raw)
In-Reply-To: <20140731.122244.665794236590108427.davem@davemloft.net>

On 7/31/2014 10:22 PM, David Miller wrote:
> From: Vivek Goyal <vgoyal@redhat.com>
> Date: Thu, 31 Jul 2014 09:07:56 -0400
> 
>> If there are performance implications of low memory profile, then user
>> needs to live with it. Otherwise they should not use low_memory_env
>> boot option to begin with.
> 
> I personally think we should avoid changing scripts, by having a kdump
> kernel force this low_mem profile to be true.
Hi,

Is there work needed to be done on those patches? It seems that the
approach taken by those patches is accepted at the end. Also, Vivek
Goyal has acked it.

This patch is fixing stuff [1] that got into last 'net-next' (3.17).
Should I wait for it to appear in the next 'net' and send the patchset
to 'net' or can I send it now to 'net-next'?

[1] ea1c1af ("net/mlx4_en: Reduce memory consumption on kdump kernel")
    and
    2599d85 ("net/mlx4_core: Use low memory profile on kdump kernel")

Thanks,
Amir

> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      parent reply	other threads:[~2014-08-06  8:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 14:59 [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 1/3] crash_dump: " Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 2/3] net/mlx4: Use is_kdump_kernel() to detect kdump kernel Amir Vadai
2014-07-27 14:59 ` [PATCH net-next 3/3] net/bnx2x: " Amir Vadai
2014-07-28  0:48 ` [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules Andi Kleen
2014-07-28 12:26   ` Vivek Goyal
2014-07-29 23:46     ` David Miller
2014-07-30 12:35       ` Vivek Goyal
2014-07-31  6:51         ` Amir Vadai
2014-07-31 13:07           ` Vivek Goyal
2014-07-31 19:22             ` David Miller
2014-08-01 12:44               ` Vivek Goyal
2014-08-06  8:10               ` Amir Vadai [this message]

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=53E1E2EA.6020102@mellanox.com \
    --to=amirv@mellanox.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=vgoyal@redhat.com \
    --cc=yevgenyp@mellanox.com \
    /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.