From: Arun Sharma <arun.sharma@intel.com>
To: rddunlap@osdl.org ("Randy.Dunlap")
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving "special" port numbers in the kernel ?
Date: 15 Nov 2002 17:46:21 -0800 [thread overview]
Message-ID: <u65uyb82a.fsf@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211151658010.6746-100000@dragon.pdx.osdl.net>
rddunlap@osdl.org ("Randy.Dunlap") writes:
> Look in arch/i386/kernel/setup.c (in 2.4.19):
>
> There is this array:
> struct resource standard_io_resources[] = ...
> that you could add to; you could even make the addition a CONFIG_ option.
That's reserving I/O ports. Are you suggesting that we create an
analogous array for IP ports ?
-Arun
next prev parent reply other threads:[~2002-11-16 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 0:00 Reserving "special" port numbers in the kernel ? Arun Sharma
2002-11-16 0:11 ` Xavier Bestel
2002-11-16 0:53 ` Arun Sharma
2002-11-16 0:58 ` Sean Neakums
2002-11-16 1:00 ` Randy.Dunlap
2002-11-16 1:46 ` Arun Sharma [this message]
2002-11-16 2:03 ` Randy.Dunlap
2002-11-16 2:43 ` Alan Cox
2002-11-17 16:37 ` Arun Sharma
2002-11-17 22:59 ` Alan Cox
2002-11-16 7:30 ` Willy Tarreau
2002-11-17 0:03 ` Chris Wedgwood
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=u65uyb82a.fsf@unix-os.sc.intel.com \
--to=arun.sharma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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