Re: max_loop limit
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Date: Thu, 22 Mar 2007 16:22:40 +0100
On Thu, 2007-03-22 at 07:11 -0700, William Lee Irwin III wrote:
On Thu, Mar 22 2007, Eric Dumazet wrote:
Sure, but it's the first Tomas patch :)
On Thu, Mar 22, 2007 at 02:54:57PM +0100, Jens Axboe wrote:
The more the reason to guide him in the direction of a right solution,
instead of extending the current bad one!
On Thu, Mar 22 2007, Eric Dumazet wrote:
Apparently the 'current crap' didnt caugth someone else attention.
On Thu, Mar 22, 2007 at 02:54:57PM +0100, Jens Axboe wrote:
I guess most people don't care, 8 is enough for them and the wasted
memory isn't too much to care about - 8 devices and only one used, is
wasting at least ~14kb on my machine here.
Any chance we can get some kind of devices set up for partitions of
loop devices if we're going to redo loopdev setup? That's been a thorn
in my side for some time.
you can already do that with devmapper and partx combo...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- max_loop limit
- From: Tomas M
- Re: max_loop limit
- From: markus reichelt
- Re: max_loop limit
- From: Tomas M
- Re: max_loop limit
- From: Eric Dumazet
- Re: max_loop limit
- From: Jens Axboe
- Re: max_loop limit
- From: Eric Dumazet
- Re: max_loop limit
- From: Jens Axboe
- Re: max_loop limit
- From: William Lee Irwin III
- max_loop limit
- Prev by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Next by Date: Re: [1/6] 2.6.21-rc4: known regressions
- Previous by thread: Re: max_loop limit
- Next by thread: Re: max_loop limit
- Index(es):
Relevant Pages
|