[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150621100329.GA5915@lst.de>
Date: Sun, 21 Jun 2015 12:03:29 +0200
From: Christoph Hellwig <hch@....de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: axboe@...nel.dk, linux-nvdimm@...ts.01.org, boaz@...xistor.com,
toshi.kani@...com, Vishal Verma <vishal.l.verma@...ux.intel.com>,
Neil Brown <neilb@...e.de>,
Greg KH <gregkh@...uxfoundation.org>,
Dave Chinner <david@...morbit.com>,
linux-kernel@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Jens Axboe <axboe@...com>, linux-acpi@...r.kernel.org,
Jeff Moyer <jmoyer@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-fsdevel@...r.kernel.org,
hch@....de, mingo@...nel.org
Subject: Re: [PATCH 03/15] nd_btt: atomic sector updates
> +config ND_MAX_REGIONS
> + int "Maximum number of regions supported by the sub-system"
> + default 64
> + ---help---
> + A 'region' corresponds to an individual DIMM or an interleave
> + set of DIMMs. A typical maximally configured system may have
> + up to 32 DIMMs.
> +
> + Leave the default of 64 if you are unsure.
Having static limits in Kconfig is a bad idea. What prevents you
from handling any (reasonable) number dynamically?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists