linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "dada1" <dada1@cosmosbay.com>
To: Rik van Riel <riel@conectiva.com.br>, Benjamin LaHaise <bcrl@redhat.com>
Cc: Andrew Morton <akpm@digeo.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] remove hugetlb syscalls
Date: Thu, 14 Nov 2002 09:52:33 +0100	[thread overview]
Message-ID: <08a601c28bbb$2f6182a0$760010ac@edumazet> (raw)
In-Reply-To: <Pine.LNX.4.44L.0211132239370.3817-100000@imladris.surriel.com>

I beg to differ.

I already use the syscalls.

The patch doesnt change Documentation/vm/hugetlbpage.txt

How one is supposed to use hugetlbfs ? That's not documented.

Before dropping support for syscalls, please change the Documentation.

Thanks

----- Original Message -----
From: "Rik van Riel" <riel@conectiva.com.br>
To: "Benjamin LaHaise" <bcrl@redhat.com>
Cc: "Andrew Morton" <akpm@digeo.com>; <linux-mm@kvack.org>;
<linux-kernel@vger.kernel.org>
Sent: Thursday, November 14, 2002 1:42 AM
Subject: Re: [patch] remove hugetlb syscalls


> On Wed, 13 Nov 2002, Benjamin LaHaise wrote:
>
> > Since the functionality of the hugetlb syscalls is now available via
> > hugetlbfs with better control over permissions, could you apply the
> > following patch that gets rid of a lot of duplicate and unnescessary
> > code by removing the two hugetlb syscalls?
>
> #include <massive_applause.h>
>
> Yes, lets get rid of this ugliness before somebody actually
> finds a way to use these syscalls...
>
> regards,
>
> Rik
> --
> Bravely reimplemented by the knights who say "NIH".
> http://www.surriel.com/ http://guru.conectiva.com/
> Current spamtrap:  <a
href=mailto:"october@surriel.com">october@surriel.com</a>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-11-14  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 23:45 Benjamin LaHaise
2002-11-14  0:42 ` Rik van Riel
2002-11-14  8:52   ` dada1 [this message]
2002-11-14 14:13     ` Christoph Hellwig
2002-11-14 15:13       ` dada1
2002-11-14 15:31         ` Benjamin LaHaise
2002-11-14 15:38           ` dada1
2002-11-14 20:11           ` Rohit Seth
2002-11-14 20:36             ` William Lee Irwin III
     [not found]           ` <3DD3FED2.2010901@unix-os.sc.intel.com>
2002-11-14 20:01             ` Benjamin LaHaise
2002-11-14 21:06             ` Benjamin LaHaise
2002-11-14 20:30 ` William Lee Irwin III
2002-11-14 20:48   ` Benjamin LaHaise
2002-11-14 21:02     ` William Lee Irwin III
2002-11-14 21:11       ` Benjamin LaHaise
2002-11-14 21:31         ` William Lee Irwin III
2002-11-14 21:40         ` Rohit Seth
2002-11-14 21:59           ` Benjamin LaHaise
2002-11-14 21:06   ` Benjamin LaHaise
2002-11-14 21:06   ` Benjamin LaHaise
2002-11-14 22:12 Seth, Rohit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='08a601c28bbb$2f6182a0$760010ac@edumazet' \
    --to=dada1@cosmosbay.com \
    --cc=akpm@digeo.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox