Re: Improve lseek scalability v3

From: Andi Kleen <andi(at)firstfloor(dot)org>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Matthew Wilcox <matthew(at)wil(dot)cx>, Andi Kleen <andi(at)firstfloor(dot)org>, viro <viro(at)zeniv(dot)linux(dot)org(dot)uk>, linux-fsdevel <linux-fsdevel(at)vger(dot)kernel(dot)org>, linux-kernel <linux-kernel(at)vger(dot)kernel(dot)org>, robertmhaas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve lseek scalability v3
Date: 2011-09-16 17:50:27
Message-ID: 20110916175027.GF7761@one.firstfloor.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> One other thing we're interested in is portability. I mean, even if
> Linux were to introduce a new hypothetical syscall that was able to
> return the file size at a ridiculously low cost, we probably wouldn't
> use it because it'd be Linux-specific. So an improvement of lseek()
> seems to be the best option.

Fully agreed. It doesn't make any sense at all to implement special
syscalls just to workaround a basic system call not scaling.

-Andi

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2011-09-16 18:13:32 Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Previous Message Alvaro Herrera 2011-09-16 17:39:50 Re: Improve lseek scalability v3