Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)

On Friday 26 October 2007 10:44, Peter wrote:
> > ...the way the watermarks work they will be evenly distributed
> > over the appropriate zones. ..

Hi Peter,

The term is "highwater mark" not "high watermark".  A watermark is an 
anti-counterfeiting device printed on paper money.  "Highwater" is how 
high water gets, which I believe is the sense we intend in Linux.  
Therefore any occurrence of "watermark" in the kernel source is a 
spelling mistake, unless it has something to do with printing paper 
money.

While fixing this entrenched terminology abuse in our kernel source may 
be difficult, sticking to the correct English on lkml is quite easy :-)

Regards,

Daniel
-
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: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
  - From: Pavel Machek <[email protected]>

Prev by Date: Re: [PATCH 1/9] Unionfs: security convert lsm into a static interface fix
Next by Date: [PATCH] 0/3 fs/ioctl.c coding style, rename vfs_ioctl/do_ioctl
Previous by thread: Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
Next by thread: [PATCH] proc: Fix proc_kill_inodes to kill dentries on all proc superblocks
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]