Re: [patch] optimise loop driver a bit

Nick Piggin <[email protected]> wrote:
>
> Looks like locking can be optimised quite a lot.

So I've peered suspiciously at the ->lo_pending handling for some time and
am unconvinced.  Are you sure that the error path in loop_make_request() is
correct?  The old code decremented the pending count in there.

Why do we need that nasty-looking `pending' local in loop_thread()?
-
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/

---

• Follow-Ups:
  • Re: [patch] optimise loop driver a bit
    • From: Nick Piggin <[email protected]>

• References:
  • [patch] optimise loop driver a bit
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: [patch] __block_write_full_page bug
• Next by Date: Re: [PATCH] private mounts
• Previous by thread: [patch] optimise loop driver a bit
• Next by thread: Re: [patch] optimise loop driver a bit
• Index(es):
  • Date
  • Thread

[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]