Alex Tomas wrote:
Jeff Garzik (JG) writes:
JG> Think about how this will be deployed in production, long term.
JG> If extents are not made default at some point, then no one will use
JG> the feature, and it should not be merged.
sorry, I disagree. for example, NUMA isn't default and shouldn't be.
but we have it in the tree and any one may choose to use it. the same
with extents. let's have it in. but let's make clear it's experimental,
it makes sense for large files only, it isn't backward compatible and
so on.
NUMA _is_ on by default, in newer hardware kernels :) K8 is NUMA by
default, remember.
But anyway... the "it's experimental" argument is _completely_
irrelevant. You have to think about the day when it is not, and how
that will get deployed, and what are the potential problems that will
arise from deployment.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
