Not really. They are near everywhere used for slow paths.
It does not make much difference anyways: Function calls are fast enough
on modern CPUs, and having a smaller text segment is probably even faster
(because it increases the cache hits). When the function is called multiple
times and is longer than a few instructions it is usually a loss
[at least according to the AMD K7 and modern Intel optimizations guides]
>
> Two more notes while I'm on the subject--
>
> My previous patch was missing a necessary but simple mm.h change.
> Updated patch attached (not including the stuff above.. yet).
>
> I've seen some comments saying that a VM pressure operation should occur
> in address_space or some VFS or buffer-related area. It would be nice
> to be able to notify some of the smarter device drivers of VM pressure
> as well... the interface presented here is independent of any VFS,
> address_space, or buffer-related operations, while at the same time
> being called at a familiar place (do_try_to_free_pages) with familiar
> arguments (priority, gfp_mask) and a familiar return value (pages freed,
> if any).
I personally think that doing it via address_space is the wrong way
(because it is not really a good way to express multiple pages that are
flushed together), but again I leave it for the MM gurus to hash out
the details.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/