Re: Avoiding external fragmentation with a placement policy Version 12

From: Dave Hansen <[email protected]>
Date: Fri, 03 Jun 2005 09:43:00 -0700

> Are those loopback allocations GFP_KERNEL?

It depends :-)  Most of the time, the packets will be
allocated at sendmsg() time for the user, and thus GFP_KERNEL.

But the flags may be different if, for example, the packet
is being allocated for the NFS client/server code, or some
asynchronous packet generated at software interrupt time
(TCP ACKs, ICMP replies, etc.).
-
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/

---

• References:
  • Re: Avoiding external fragmentation with a placement policy Version 12
    • From: Nick Piggin <[email protected]>
  • Re: Avoiding external fragmentation with a placement policy Version 12
    • From: "Martin J. Bligh" <[email protected]>
  • Re: Avoiding external fragmentation with a placement policy Version 12
    • From: Dave Hansen <[email protected]>

• Prev by Date: Re: [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
• Next by Date: Re: [patch] broken fault_in_pages_readable call in generic_file_buffered_write.
• Previous by thread: Re: Avoiding external fragmentation with a placement policy Version 12
• Next by thread: Re: Avoiding external fragmentation with a placement policy Version 12
• 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]