Re: Compiling C++ modules

On Monday 24 April 2006 23:50, you wrote:
> Oh, and yeah, a = b + c *is* more readable than
> 
> a = malloc(strlen(b) + strlen(c));
> strcpy(a,b);
> strcat(a,c);
> 
> and contains fewer bugs ;)

and a hidden memory allocation.
Which GFP flag would you use for the allocation?
(And how would you actually _pass_ it)
GFP_KERNEL? Good luck, if you see a
a = b + c;
in atomic context.
GFP_ATOMIC? Well, we both don't want that.
Checking is_atomic() and deciding upon that?
I call that overhead... .

-- 
Greetings Michael.

Attachment: pgp9Y7JSyNfh1.pgp
Description: PGP signature

---

• References:
  • Compiling C++ modules
    • From: Gary Poppitz <[email protected]>
  • Re: Compiling C++ modules
    • From: Kyle Moffett <[email protected]>
  • Re: Compiling C++ modules
    • From: "marty fouts" <[email protected]>

• Prev by Date: Is there an easy way to collect how much memory is used for page cache?
• Next by Date: Re: question about nfs_execute_read: why do we need to do lock_kernel?
• Previous by thread: Re: Compiling C++ modules
• Next by thread: Re: Compiling C++ modules
• 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]