From: Sam Coles <sam@bcinet.net>
To: shreenivasa H V <shreenihv@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Could clock granularity be increased????
Date: 05 May 2001 14:34:14 -0400 [thread overview]
Message-ID: <989087664.885.0.camel@sam> (raw)
In-Reply-To: <20010505175314.7785.qmail@nwcst288.netaddress.usa.net>
In-Reply-To: <20010505175314.7785.qmail@nwcst288.netaddress.usa.net>
Will editing include/asm/param.h not do the trick?
Sam
On 05 May 2001 12:53:14 -0500, shreenivasa H V wrote:
> Hi,
>
> Is there any way I could use a clock granularity of less than 10ms if I need
> to do some hacking of the kernel TCP code? Ideally I would require the
> interval of the order of 10-100 microseconds.
> thanks,
> shreeni.
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
> -
> 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/
prev parent reply other threads:[~2001-05-05 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 17:53 Could clock granularity be increased???? shreenivasa H V
2001-05-05 18:34 ` Sam Coles [this message]
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=989087664.885.0.camel@sam \
--to=sam@bcinet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shreenihv@usa.net \
/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