From: David Miller <davem@davemloft.net>
To: jbenc@redhat.com
Cc: netdev@vger.kernel.org, richardcochran@gmail.com
Subject: Re: [PATCH net-next] ptp: increase the maximum number of clocks
Date: Thu, 21 Mar 2013 17:20:17 -0400 (EDT) [thread overview]
Message-ID: <20130321.172017.1499060411785395307.davem@davemloft.net> (raw)
In-Reply-To: <d219aa87bd5b3e2fa42449720d845a7110f642f0.1363893841.git.jbenc@redhat.com>
From: Jiri Benc <jbenc@redhat.com>
Date: Thu, 21 Mar 2013 20:24:19 +0100
> As network adapters supporting PTP are becoming more common, machines with
> many NICs suddenly have many PHCs, too. Although the PHCs are not used in
> such cases, they produce error messages like this:
>
> igb 0000:07:00.0: ptp_clock_register failed
>
> Currently, the maximum number of devices accepted by ptp_clock_register
> is 8 which is pretty low. We could silence the error messages but this would
> hurt in case somebody wants to use one of the interfaces to actually run
> PTP, as the /dev/ptp%d device for the desired interface may or may not be
> available after each boot.
>
> Let's increase the maximum to 128. This shouldn't be a problem, as for the
> char devices, the whole major number is reserved anyway, and 128bit bitmap
> isn't a big deal, either.
>
> Signed-off-by: Jiri Benc <jbenc@redhat.com>
This really needs to be dynamic, and it shows what a bad idea it was
to use character drivers for this which introduces arbitrary device
arity limitations.
I want to see a better solution to this problem than just bumping this
limit arbitrarily every once in a while.
I'm not apply this patch, we're better than this.
next prev parent reply other threads:[~2013-03-21 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 19:24 [PATCH net-next] ptp: increase the maximum number of clocks Jiri Benc
2013-03-21 21:20 ` David Miller [this message]
2013-03-23 17:59 ` Richard Cochran
2013-03-23 23:53 ` David Miller
2013-03-25 16:08 ` Jiri Benc
2013-03-25 18:51 ` Richard Cochran
2013-03-25 21:39 ` Ben Hutchings
2013-03-26 9:48 ` Jiri Benc
2013-03-26 18:44 ` Richard Cochran
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=20130321.172017.1499060411785395307.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).